|
I'll use the template but this this is probably a more flexible thing (I normally scream about x-instead-of-y but I don't care here). I'm also using fake names. Problem description: I have a Wordpress site at https://www.originalsite.com pointing to a Ramnode VPS instance. It is running Ubuntu 20.04 now after an upgrade with apache2 serving out of /var/www/originalsite.com/public_html. I now have https://www.newsite.com that I'd like to serve out of /var/www/newsite.com/public_html. I want to ensure the browser shows newsite.com and doesn't show originalsite.com when it serves newsite's pages. I started setting up a virtual host for it using the apache configuration, but certbot couldn't resolve newhost's name. I'm not surprised, but I also don't really know how I'm supposed to set up this second host name to point to the same IP but serve the other pages instead. Attempted ... stuff: I have a cpanel DNS set up for https://www.originalsite.com in Ramnode. That was in 2018 or so and I don't even remember how I did it. I want to know if the normal thing here is to set up a separate cpanel DNS for https://www.newsite.com through a ticket or whatever. Is that what I am supposed to do? I've since just set up an A record for @ to from newsite.com to point to the VPS' IP address. This will take some time to propagate, but I am pretty sure I'm not out of the woods just doing this. The original cpanel DNS configuration then gave me some nsX.ramnode.com name servers to give to Namecheap, which is my provider. This configuration seems fine. Blindly setting newsite.com to use the same nameservers doesn't work. Again, no surprise. How would Ramnode's nameservers know? I am opening a support ticket with ramnode to figure out the deal with the cpanel DNS too. I don't know if I have to open up my wallet for it or whatever. Operating system: Ubuntu 20.04. It was Ubuntu 18.04 until this morning when I did a distribution update. The old site worked afterwards. I don't have any errors here, although there was a moment where apache2-doc refused to configure and blocked a bunch of crap. I had to purge and reinstall. Bizarre. System specs: It's a Ramnode VPS with something like 8GB of RAM. Location: US I have Googled and read the FAQ: Yes. There's a bunch of new and old, incomplete stuff about this but between DNS having a propagation delay and me just not really being familiar with this, I am just loving it up.
|
#
?
Jul 6, 2022 19:01
|
|
|
|
| # ? Apr 29, 2024 19:25 |
|
|
I ultimately got it when the DNS propagated and certbot could finish generating certificates. The new site still has an A record pointing to a static IP. I am figuring out if I can do that better because I don't think that address is permanent.
|
|
#
?
Jul 6, 2022 23:03
|
|
|
Rocko Bonaparte posted:I ultimately got it when the DNS propagated and certbot could finish generating certificates. The new site still has an A record pointing to a static IP. I am figuring out if I can do that better because I don't think that address is permanent. the new domain name needs to be pointed to your ramnode vps IP address, atleast newsite.com the https://www.newsite.com can be a CNAME record. The ip address should be static for your subscription and the only chance it would change is if you delete the Vps server.
|
|
#
?
Jul 17, 2022 01:36
|
|