I installed a 1-click droplet with WordPress on LiteSpeed server, created an A record at the domain’s registrar pointing the domain to the droplet’s IP address, and also, on the DigitalOcean side, added the domain under Networking which created 3 NS and 1 A records.
So far so good.
I can see the site if I load it in browser using the droplet’s IP address but do not see it if I use the domain. When I type the domain, the browser throws a 404 error.
This page from LiteSpeed seems like providing a solution but when I try to access the server’s control panel via 7080 port, the page times out.
Can anyone suggest a fix please?
I have already created a ticket with DO but no response yet, this is somewhat urgent.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
To access web admin port 7080, please run the following command to allow port 7080.
Then, please go to web admin > Listeners and set
*to both HTTP and HTTPS domain values, do a graceful restart
Please let us know if it helps.
Maybe the domain name is not resolving to the correct IP address yet? DNS changes tend to take some time, so I’d give it at least 24 hours, especially if there was an actual nameserver change involved.
Also, you don’t need the domain or DNS records on DigitalOcean, unless you’re going to use the DigitalOcean DNS servers for your domain, by changing the name servers to: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com at the domain registrar.
Finally, you can use https://dnschecker.org to check if your domain points to the correct IP address from different parts of the world, pretty handy in debugging DNS problems.
If the domain name is correctly pointed to your IP, then there might be a misconfiguration in the web server.
Hope that helps.