Nginx connects successfully with curl, but times out of browser

Asked 2 years ago, Updated 2 years ago, 80 views

This is Ubuntu 20.04.
After installing sudo apt install nginx, I connected to the IP of the server with curl, and the html of the welcome page of Nginx came back.
However, if you connect to the same IP in your browser, it times out.
There is nothing in the Nginx log.

Nginx Configuration 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.
# # https://www.nginx.com/resources/wiki/start/
# # https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/
# # https://wiki.debian.org/Nginx/DirectoryStructure
#
# In most cases, administrators will remove this file from sites-enabled / and
# leave it as reference inside of sites-available where it will continue to be
# updated by the nginx packaging team.
#
# This file will automatically load configuration files provided by other
# applications, such as Drupal or Wordpress. These applications will be made
# available under a path with that package name, such as/drupal 8.
#
# Please see /usr/share/doc/nginx-doc/examples/for more detailed examples.
##

# Default server configuration
#
server{
        listen80 default_server;
        listen [::]:80 default_server;

        # SSL configuration
        #
        # listen443 ssl default_server;
        # listen [::]:443 ssl default_server;
        #
        # Note: You should disable gzip for SSL traffic.
        # See: https://bugs.debian.org/773332
        #
        # Read up on ssl_ciphers to secure a secure configuration.
        # See: https://bugs.debian.org/765782
        #
        # Self-signed certificates generated by the ssl-cert package
        # Don't use them in a production server!
        #
        # include snippets/snakeoil.conf;

        root/var/www/html;

        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html;

        server_name_;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files$uri$uri/=404;
        }

        # pass PHP scripts to FastCGI server
        #
        # location~\.php${
        #       include snippets/fastcgi-php.conf;
        #
        #       # With php-fpm (or other unix sockets):
        #       fastcgi_pass unix:/var/run/php/php 7.0-fpm.sock;
        #       # With php-cgi (or other tcp sockets):
        #       fastcgi_pass 127.0.0.1:9000;
        #}

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


# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/and symlink that
# to sites-enabled/to enable it.
#
# server {
#       listen80;
#       listen [::]:80;
#
#       server_name example.com;
#
#       root/var/www/example.com;
#       index index.html;
#
#       location / {
#               try_files$uri$uri/=404;
#       }
#}

The configuration file remains the default and is not being tampered with.

Is there a solution?

ubuntu nginx

2022-09-30 20:21

1 Answers

It was caused by the packet filtering function of Sakura VPS.
It was resolved by opening TCP 80/443 from the administration page.


2022-09-30 20:21

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.