Question
Transferred Digital Ocean Droplet, new IP throws 404 not found
- Posted May 27, 2020
- LaravelDigitalOcean
Hello All. So I created a Digital Ocean droplet using Laravel Forge and linked it to a github repo…added a domain name, and setup SSL . As the project was wrapped up I wanted to transfer ownership of the droplet to my client so I followed instructions here. After doing so the IP address used by the new droplet throws a 404 Not found | nginx/1.17.3. I’m suspicious this might have something to do with the SSL certificate? Any help is appreciated.
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 @yodergilbert1,
I believe that you have a separate Nginx server block for your domain name. To check that SSH to the new Droplet and then run the following command:
- ls -lah /etc/nginx/sites-enabled
In that folder, you will see all of your enabled Nginx server blocks.
What you could do is disable the default config so that you are left only with the actual Nginx server block for your Laravel application.
To disable the default config you can use the following:
unlink /etc/nginx/sites-enabled/your_default_conf
And then restart Nginx:
systemctl restart nginx
Hope that this helps. Regards, Bobby
Try DigitalOcean for free
Click below to sign up and get $100 of credit to try our products over 60 days!
I’m also having the exact same problem!