That being said, the one-click images are meant to be a starting point. You still need to know how to manage a server, setup the server, etc. Server/System administration, much like coding, isn't a one-time deal that requires no further setup, configuration, or tweaking/tuning -- it's on-going.

There's quite a bit that repository packages leave out and in turn, guides do the same -- mainly because we'd see 5-10 page guides on configuration if they covered every single detail about nginx.conf or server block configuration (they'd each be a mini-book of their own).

There's also plenty of ways to reduce redundancies in configuration -- for example, there's no need to include that index line in every server block. Remove it from server blocks and place it in nginx.conf, reload/restart, and don't worry about it. This sets it globally.

If you need to work with a variety of indexes, you can expand the line:

index index.php index.html index.html index.js, index.shtml;

etc. -- I'd only include the ones you know you'll be using, but that's an example of what you could do.

If you have any other questions / issues, feel free to reply -- I'll be more than happy to help!

Yeah, turns out that the server was not using the Default file it was using one called digitalocean to manage, so no matter what changes i did to the default file (or even create a new one for that matter) it would not work.

Now i'm facing another issue, I deleted the digitalocean file and now its not handling requests, how do i go about selecting the default file or the other that I created to handle said requests?

Open up /etc/nginx/nginx.conf and find the include line at the bottom. That'll tell you where NGINX is pulling files from. In most all cases, for repositories, that'll be /etc/nginx/sites-enabled.

You can change that to any directory. Personally, I don't like having to bother with symlinks, so I change sites-enabled to sites-available and then stick all configuration files in that directory.

As a general note, you're not confined to using either of those directories. You could create a new directory, /etc/nginx/sites and stick your configuration files in there and change the include line to use that directory instead.

...

I mainly suggest using sites-available or a new directory and changing the include line so you don't have to bother with symlinks. They're a pain and really offer no real benefit -- even on servers with hundreds of them.

..

At the end of the day, NGINX will load files from wherever you tell it to :-). As long as the file exists in the directory you tell NGINX to use, it'll load that file.

You may add here your
server {
}
statements for each of your virtual hosts to this file
You should look at the following URL's in order to grasp a solid understanding
of Nginx configuration files in order to fully unleash the power of Nginx.
http://wiki.nginx.org/Pitfalls
http://wiki.nginx.org/QuickStart
http://wiki.nginx.org/Configuration
Generally, you will want to move this file somewhere, and start with a clean
file but keep this around for reference. Or just disable in sites-enabled.
Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.

@Vanker
Okay, which sites do you have defined in /etc/nginx/sites-enabled. You need to look through every configuration and make sure none of them are overlapping.
If you don't know what to do, then just post each server block, but please use the code-button in this editor.

When using the Nginx web server, server blocks (similar to the virtual hosts in Apache) can be used to encapsulate configuration details and host more than one domain off of a single server. In this guide, we'll discuss how to configure server blocks in Nginx on an Ubuntu...

Also, your link did not worked as well, it says to create a new "block-file" in the sites-enabled but if the default was already enabled and if i correctly set that up isn't supposed to be working anyway?

One other thing, ~~/sites-enabled/"example.com" (this isn't supposed to be the domain right?) just a name for you to better find what you are looking for

If you only use one site, then just edit whatever file is located in /etc/nginx/sites-enabled

If you want to run multiple sites on the one-click installation, then I would recommend that you remove all files in /etc/nginx/sites-enabled/* and /etc/nginx/sites-available/*, and then create a new configurations by following the tutorial.

In the tutorial, everything with the color red are something you should modify.

When using the Nginx web server, server blocks (similar to the virtual hosts in Apache) can be used to encapsulate configuration details and host more than one domain off of a single server. In this guide, we'll discuss how to configure server blocks in Nginx on an Ubuntu...