I bought vps on ubuntu 14.04. ssh works, the server is pinged, the nginks are configured according to the initial manual. But when driving ip into the browser, the Nginks homepage is not. because the server is needed for a jango site, I also checked it with uWSGI, but there is also no plug in the browser, technical support says that everything is fine with them. The question is - what did I do wrong? nginx.conf

 user www-data;
 worker_processes 2;
 pid /run/nginx.pid;

 events {
     worker_connections 768;
     # multi_accept on;
 }

 http {

     ##
     # Basic Settings
     ##

     sendfile on;
     tcp_nopush on;
     tcp_nodelay on;
     keepalive_timeout 65;
     types_hash_max_size 2048;
     # server_tokens off;

     # server_names_hash_bucket_size 64;
     # server_name_in_redirect off;

     include /etc/nginx/mime.types;
     default_type application / octet-stream;

     ##
     # Logging Settings
     ##

     access_log /var/log/nginx/access.log;
     error_log /var/log/nginx/error.log;

     ##
     # Gzip Settings
     ##

     gzip on;
     gzip_disable "msie6";

     # gzip_vary on;
     # gzip_proxied any;
     # gzip_comp_level 6;
     # gzip_buffers 16 8k;
     # gzip_http_version 1.1;
     # gzip_types text / plain text / css application / json application / x javascript text / xml application / xml application / xml + rss text / javascript;

     ##
     # nginx-naxsi config
     ##
     # Uncomment it if you installed nginx-naxsi
     ##

     #include /etc/nginx/naxsi_core.rules;

     ##
     # nginx-passenger config
     ##
     # Uncomment it if you installed nginx-passenger
     ##

     #passenger_root / usr;
     #passenger_ruby / usr / bin / ruby;

     ##
     # Virtual Host Configs
     ##

     include /etc/nginx/conf.d/*.conf;
     include / etc / nginx / sites-enabled / *;
 }

 # mail {
 # # See sample authentication script at:
 # # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
 # 
 # # auth_http localhost / auth.php;
 # # pop3_capabilities "TOP" "USER";
 # # imap_capabilities "IMAP4rev1" "UIDPLUS";
 # 
 # server {
 # listen localhost: 110;
 # protocol pop3;
 # proxy on;
 #}
 # 
 # server {
 # listen localhost: 143;
 # protocol imap;
 # proxy on;
 #}
 #} 

sites-available / default

  # You may add here your
  server {
     listen 80;
     server_name mydomain.net;
     root /var/www/html/test.ru;
  }
 # of statements for this file

 ##
 # You should look at the following URL
 # 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 want to move this file
 # file but keep this around for reference.  Or just disable sites-enabled.
 #
 # Please see / usr / share / doc / nginx-doc / examples / for more detailed examples.
 ##

 server {
     listen 80;
     listen [::]: 80 default_server ipv6only = on;

     root / usr / share / nginx / html;
     index index.html index.htm;

     # Make site accessible from http: // localhost /
     server_name localhost;

     location / {
         # First attempt to file request
         # as directory, then fall back to displaying a 404.
         try_files $ uri $ uri / = 404;
         # Uncomment to enable naxsi on this location
         # include /etc/nginx/naxsi.rules
     }

     # Only for nginx-naxsi used with nginx-naxsi-ui: process denied requests
     #location / RequestDenied {
     # proxy_pass http://127.0.0.1:8080;    
     #}

     #error_page 404 /404.html;

     # redirect server error pages to the static page /50x.html
     #
     #error_page 500 502 503 504 /50x.html;
     #location = /50x.html {
     # root / usr / share / nginx / html;
     #}

     # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
     #
     #location ~ \ .php $ {
     # fastcgi_split_path_info ^ (. + \. php) (/.+) $;
     # # NOTE: You should have "cgi.fix_pathinfo = 0;"  in php.ini
     #
     # # With php5-cgi alone:
     # fastcgi_pass 127.0.0.1:9000;
     # # With php5-fpm:
     # fastcgi_pass unix: /var/run/php5-fpm.sock;
     # fastcgi_index index.php;
     # include fastcgi_params;
     #}

     # deny access to .htaccess files, if Apache's document root
     # concurs with nginx's one
     #
     #location ~ /\.ht {
     # deny all;
     #}
 }


 # another virtual host using mix of IP, name-, and port-based configuration
 #
 #server {
 # listen 8000;
 # listen somename: 8080;
 # server_name somename alias another.alias;
 # root html;
 # index index.html index.htm;
 #
 # location / {
 # try_files $ uri $ uri / = 404;
 #}
 #}


 # Https server
 #
 #server {
 # listen 443;
 # server_name localhost;
 #
 # root html;
 # index index.html index.htm;
 #
 # ssl on;
 # ssl_certificate cert.pem;
 # ssl_certificate_key cert.key;
 #
 # ssl_session_timeout 5m;
 #
 # ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2;
 # ssl_ciphers "HIGH:! aNULL:! MD5 or HIGH:! aNULL:! MD5:! 3DES";
 # ssl_prefer_server_ciphers on;
 #
 # location / {
 # try_files $ uri $ uri / = 404;
 #}
 #}

Closed due to the fact that it was off topic by aleksandr barakin , user194374, zRrr , αλεχολυτ , Grundy Jul 3 '16 at 6:44 .

It seems that this question does not correspond to the subject of the site. Those who voted to close it indicated the following reason:

  • "The question is caused by a problem that is no longer reproduced or typed . Although similar questions may be relevant on this site, solving this question is unlikely to help future visitors. You can usually avoid similar questions by writing and researching a minimum program to reproduce the problem before publishing the question. " - aleksandr barakin, Community Spirit, zRrr, αλεχολυτ, Grundy
If the question can be reformulated according to the rules set out in the certificate , edit it .

  • one
    Please bring the nginx configs - how did you set up the server for work? - cheops 6:51 pm
  • added, and at the same time in the terminal server curl displays the stub nginx, but there is no access from another machine. - Pirate

1 answer 1

Everything was decided, it turned out that the Ubuntov firewall did not have permission to the port of Nginka, blunted the sponge.