Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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.
Hi there @CanuckLuck,
I’ve seen the same behavior when the document root directory is not readable or writable by the Nginx user.
What I could suggest is making sure that your /var/www/prairiestormpaintball.com/html folder has the same permissions and ownership as the /var/www/anchoridea.com/html folder.
Also what I could suggest is checking your Nginx error log to see if there’s some more information about the problem:
- tail -100 /var/log/nginx/error.log
Let me know how it goes! Regards, Bobby
Hi @CanuckLuck
I have tried to access your domains prairiestormpaintball.com, www.prairiestormpaintball.com, anchoridea.com, and www.anchoridea.com. They all point to their own website. There is no redirection. Did you fixed your problem?
The Nginx configuration files for both your original site and the new site appear to be correctly set up, with distinct server_name directives and different root directories. The issue you’re experiencing, where the third site redirects to the first site, is commonly due to Nginx not properly recognizing the server block for the new site. Here’s a checklist to troubleshoot and resolve this issue:
Make sure the new site’s configuration is symlinked in the sites-enabled directory. You can check this with ls -l /etc/nginx/sites-enabled.
After making changes to Nginx configuration files or symlinks, always reload Nginx to apply the changes:
sudo nginx -t
sudo systemctl reload nginx
server_name entries across your Nginx configuration files. Nginx will serve the first matching server block it finds, so any misconfiguration could cause it to serve the wrong site.prairiestormpaintball.com and www.prairiestormpaintball.com are correctly pointing to the IP address of your droplet.server_name. This can help identify if the issue is with Nginx’s selection of server blocks:server {
listen 80 default_server;
listen [::]:80 default_server;
server_name _;
return 444;
}
prairiestormpaintball.com, you will need to set up an SSL certificate and add a similar server block for listening on port 443, like you did for your original site.tail -f /var/log/nginx/error.log
tail -f /var/log/nginx/access.log
/var/www/prairiestormpaintball.com/html have the correct permissions and ownership for Nginx to access them.