Noob here, so please bare with me. A few months ago, I installed wordpress on Ubuntu. Everything was working fine. I got an email saying I needed to top up my DO account. Did that and that same day, I discovered the 502 error when trying to access my site. I didn’t touch or change any of the configurations so am confused as to why this is happening.
Checked the error log:
[Mon Sep 11 06:25:02.712766 2017] [core:notice] [pid 1561] AH00094: Command line: '/usr/sbin/apache2'```
Checked the DNS and found out it's not pointing to the correct IP where my droplet is. Double checked on the DO side and my domain (A record) is directed to the IP address of my droplet.
When I enter the IP address of my droplet in my browser, the same Error 502 comes up. I've waited a day, cleared out my cache, used a different browser etc, plus did a few reloads and still nothing.
What am I missing here? Desperate for a solution.
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!
Hello,
In addition to what has already been mentioned, I would recommend following these steps in case that you are having any problems with your nginx server and you are unsure on what the problem is:
systemctl status nginx
If nginx is running you should see something like this:
● nginx.service - The nginx HTTP Server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-11-19 09:37:46 UTC; 2 days ago
Docs: https://httpd.nginx.org/docs/2.4/
If nginx is not running then the output would look like this:
● nginx.service - The nginx HTTP Server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Fri 2019-11-22 08:41:01 UTC; 39s ago
Docs: https://httpd.nginx.org/docs/2.4/
systemctl start nginx
Then check the status agian and make sure that nginx remains running.
systemctl enable nginx
nginx -t
If you get an error, you would need to fix that problem and then you could restart nginx:
systemctl restart nginx
Syntax OK when running nginx -t then your confiruation is correct, so I would recommend checking your error logs:tail -f /var/log/nginx/error.log
Find the user that your nginx service is running as:
ps auxf | grep nginx
If you are using Ubuntu, the user should be www-data, so you would need to make sure that your files and folders are owned by that user, so nginx could read and write to those files:
chown -R www-data:www-data /var/www/yourdomain.com
netstat -plant | grep '80\|443'
ufw allows TCP connections on port 80 and 443:ufw status
If this is the case, you can follow the steps from this article here on how to configure your ufw:
https://www.digitalocean.com/community/tutorials/how-to-set-up-a-firewall-with-ufw-on-ubuntu-18-04
That is pretty much it, with all of the above information you should be able to narrow down the problem.
For more information I would suggest checking out this article here:
And here is also a quick video demo on how to do that as well:
Hope that this helps! Regards, Bobby Source: How to Troubleshoot Common Nginx Issues on Linux Server?
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.