Nginx Server does not start.

@kailtom

If the file is not a valid server block and it serves no actual purpose, you should be able to delete it without any issues. If that doesn’t resolve the issues you’re having though, I’d need to take a closer look at the rest of your configuration as there are so many includes in the files, it’s hard to see where the actual error is since NGINX is’t actually giving a file (which is most likely due to the number of includes).

@kailtom

The best way to get around the copy and paste issues when using nano would be to login as root to the Droplet using SFTP (using root as your username, your root password, and your Droplet IP – you’ll connect on Port 22).

After you’ve successfully logged in, navigate to your NGINX directory and download the files and then copy and paste from your local text editor.

The reason being is because in the Pastebin you just provided, the issue is with this line:

        ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA2$

As it ends with a $ instead of a ; – and that appears to be an issue as the contents of that file was copied from your terminal instance instead of from the file locally.

So you’ll need to download the main file, nginx.conf and the server blocks associated with the sites you’re hosting (i.e. all configuration files starting with server {).

@kailtom

The issues are with this server block: http://pastebin.com/x895uFGr

The first issue I’m seeing is with this line:

# Force HTTP to HTTPS
error_page 497 =200 https://$host:22222$request_uri;

The above does not force HTTP to HTTPS, it sets an error page and enforces and internal redirect. It could very well be used to push HTTP to HTTPS, though that’s not what this was actually intended for.

Ideally, you’d setup a server block that looks like this to handle HTTP (on Port 80) redirects to HTTPS (on Port 443).

server {
	listen 80 default_server;
	listen [::]:80 default_server;
	server_name _;
	return 301 https://$host$request_uri;
}

While this isn’t actually what’s causing the issue, it can result in some rather odd logs appearing since the error_page definition isn’t meant for handling redirects to SSL and should be used for it’s actual intended usage.

The actual issue, however, is that this server block is missing the closing } at the end of the file.

Below this block:

  location ~* /vimbadmin/public/(.*) {
    root /var/www/22222/htdocs/vimbadmin/public;
    try_files $uri $uri/  /vimbadmin/public/index.php?$args;
  }

You need another closing }, so it should look like:

  location ~* /vimbadmin/public/(.*) {
    root /var/www/22222/htdocs/vimbadmin/public;
    try_files $uri $uri/  /vimbadmin/public/index.php?$args;
  }
}

Why? Without that last }, you’re leaving the server { block portion open, so it’s trying to find more configuration that doesn’t exist. Simply add that last closing } and then run:

service nginx reload

and that should get you squared away. If, however, another issue pops up, please let me know and we’ll take look at that error and see what the issue is.