Glad to hear you got it working!

In the future, here’s something that might come in useful. You can check the syntax of Nginx’s configuration files by running:

nginx -t -c /etc/nginx/nginx.conf

The error output will give you a hint at what the problem is as well as the line number.

Try to run the following two commands:

sudo fuser -k 80/tcp

sudo fuser -k 443/tcp

Then execute

sudo service nginx restart

https://stackoverflow.com/questions/35868976/nginx-not-started-and-cant-start/51684856#51684856

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:

• Check if nginx is running:

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/

• If nginx is not running you could start it with:

systemctl start nginx

Then check the status agian and make sure that nginx remains running.

• If nginx did not start after a reboot, you could enable it so that it starts after the next reboot:

systemctl enable nginx

• Check your nginx config syntax:

nginx -t

If you get an error, you would need to fix that problem and then you could restart nginx:

systemctl restart nginx

• If you get 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

• Check the permissions of the files and folders in your document root:

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

• Check if nginx is binding to the default ports:

netstat -plant | grep '80\|443'

• Check if 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:

https://www.digitalocean.com/community/tutorials/how-to-troubleshoot-common-site-issues-on-a-linux-server

Hope that this helps!
Regards,
Bobby
Source: How to Troubleshoot Common Nginx Issues on Linux Server?

Heres the bug. Its fixed but not showing in Digitaocean repos fix.
You can manually edit this to work.
https://github.com/webmin/webmin/issues/206

$ service apache2 stop
$ service nginx restart

deployer@sureApp07:~$ sudo systemctl restart nginx
Job for nginx.service failed because the control process exited with error code.
See “systemctl status nginx.service” and “journalctl -xe” for details.
deployer@sureApp07:~$ systemctl status nginx.service
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2017-10-10 10:54:42 UTC; 10s ago
Docs: man:nginx(8)
Process: 8136 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
CPU: 21ms
deployer@sureApp07:~$

Any help?

If you miss the semicolon symbol “;” at the end of any statement, you may not get the error when trying to start / restart / reload nginx.

Example: Here you will get the error, as ; is missed on line no 3.

    server {
        location / {
            proxy_pass http://localhost:8080
        }

        location ~ \.(gif|jpg|png)$ {
            autoindex on;
            root /data/images;
        }
    }

I leave this here incase someone comes here looking for an answer and they experience the same problem I had.

Check if you have apache2 installed and running by typing service apache2 status. If it’s running it will prevent nginx from starting since they use the same port. So you can stop apache2 by typing service apache2 stop, then restart your nginx.