Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

jsiegle's avatar

2 Domains | 1 IP - NGINX

I have two domains on D.O set up through forge on the same server/IP, both have been active for 4 months and issue-free. https://lightpointdev.com and https://jlsdesk.com.

Originally before moving them, they were on shared cloud hosting at Bluehost which I configured to point to D.O nameservers. When the hosting plan at Bluehost ended https://jlsdesk.com (which was the primary Bluehost domain) no longer loads but gives me a non-descript error, https://lightpointdev.com still works correctly.

I have checked the nginx configs and both sites have a vhost in the config specifying their server name as :

server {
    listen xxx ssl http2;
    listen [::]:xxx ssl http2;
    server_name jlsdesk.com;
    root /xxx/xxx/jlsdesk.com/public;

and

server {
    listen xxx ssl http2;
    listen [::]:xxx ssl http2;
    server_name lightpointdev.com;
    root /xxx/xxx/lightpointdev.com/public;

I see no changes that have taken place with the exception that over on D.O under networking / Domains these two domains now show "multiple locations" in the Directs to column rather than the server name and ip address.

The nameservers are correct...the A Types are lightpointdev.com/www.lightpointdev.com | jlsdesk.com/www.jlsdesk.com the value is the correct ip . It seems as if everything should be ok. Everything is active, DNS records are published and I've verified everything that I know to do.

Am I missing a configuration I need that would replace something Bluehost did for jlsdesk.com?

Thank you in advance.

0 likes
2 replies
secondman's avatar

What do you mean by non-descript error what does the error say exactly?

Did you ping and dig the domain to make sure the DNS is correct?

It could be that Bluehost didn't destroy your DNS file, but if you've changed the nameservers at your host, or the IP at the DO DNS that shouldn't matter I don't think.

OpenDNS has a nice tool I always use when I switch servers to help update the worldwide DNS cache. It seems to work pretty well with Linode servers, I haven't used DO in quite a while.

https://cachecheck.opendns.com

Give us an update once you resolve it, this is always a good bit of knowledge to have.

jsiegle's avatar
jsiegle
OP
Best Answer
Level 6

This is one of those cases that ends in a Facepalm. I had checked all that you said (before you said it) and was totally at a loss. The non-descript error was one of those ‘whoops something went wrong”.

Finally through slack I was given the smart idea to check the laravel log. I hadn’t done this because I wrongly assumed it was a server-side issue. It wasn’t.

Somehow the landing page wasn’t loading. It wasn’t there. I don’t know what happened, how it occurred but it did and with a new commit and deploy all was fixed.

Lesson learned: explore ALL possibilities, not just the assumed possibilities.

Please or to participate in this conversation.