Certbot으로 SSL을 활성화한 후 HTTPS를 통해 내 서버에 액세스할 수 없는 문제를 해결하려면 어떤 단계를 수행해야 합니까?

Question

이 문제를 진단하고 해결하는 데 도움을 찾고 있습니다. Certbot으로 SSL을 활성화한 후 HTTPS를 통해 내 서버에 액세스할 수 없는 문제를 해결하려면 어떤 단계를 수행해야 합니까? 제가 놓쳤을 수 있는 일반적인 함정이나 구성 설정이 있습니까?

이 SSL 문제를 해결하는 데 도움이나 지침을 주시면 대단히 감사하겠습니다.

나는 이 명령 certbot 명령 sudo certbot --nginx를 사용했고 certbot 명령 이후 구문이 성공했습니다. 내 서버에 액세스할 수 없습니다. http에서는 작동하지만 https에서는 작동하지 않습니다.

이것은 사이트에서 사용 가능한 .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 underneath a path with that package name, such as /drupal8.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

# Default server configuration
#
server {
        
        #listen 443;
        #listen [::]:443;
        # SSL configuration
        #
        # listen 443 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 ensure a secure configuration.
        # See: https://bugs.debian.org/765782
        #
        # Self signed certs generated by the ssl-cert package
        # Don't use them in a production server!
        #
        # include snippets/snakeoil.conf;

        root /var/www/html/waste-management-dev/public;

        # Add index.php to the list if you are using PHP
        index index.php;

        server_name yourdomain.in;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                #try_files $uri $uri/ =404;
                try_files $uri $uri/ /index.php?q=$uri&$args;

        }

        # pass PHP scripts to FastCGI server
        #
        location ~ \.php$ {
                  try_files $uri =404;
             fastcgi_split_path_info ^(.+\.php)(/.+)$;
             include fastcgi_params;
             fastcgi_pass unix:/run/php/php7.4-fpm.sock;
             fastcgi_index index.php;
             fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
             #fastcgi_param SCRIPT_NAME $fastcgi_script_name;
             #include fastcgi_params;
        }

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

    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/yourserver.in/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/yourserver.in/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}


# 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 {
#       listen 80;
#       listen [::]:80;
#
#       server_name example.com;
#
#       root /var/www/example.com;
#       index index.html;
#
#       location / {
#               try_files $uri $uri/ =404;
#       }
#}

server {
    if ($host = yourserver.in) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


        listen 80 default_server;
        listen [::]:80 default_server;

        server_name myserver;
    return 404; # managed by Certbot


}

Answer 1

기본적으로 사소한 정보만 게시했으므로 이를 기반으로 구성이 작동할 수 있습니다.

# Default server configuration
# which means its a catch all for these that are not configured, if you use only one site, for this server you dont need a specific host
# /etc/nginx/sites-enabled/default

server {
        listen 80 default_server;
        listen [::]:80 default_server;
        root /var/www/html;
        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:/run/php/php-fpm.sock;
        #       # With php-cgi (or other tcp sockets):
        #       fastcgi_pass 127.0.0.1:9000;
        }
      location ~ \.cgi$ {
                gzip off;
                include fastcgi.conf;
                include fastcgi_params;
                fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                fastcgi_pass unix:/var/run/fcgiwrap.socket;
        }


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

}

#### NEW FILE !!!!!!
#### /etc/nginx/sites-enabled/unwaste.in 
##start file

server {
        server_name unwaste.in;
        listen 80;
        return 307 https://$host$request_uri;
}


server {
        
# enable http2 support - if module if avaible
        listen 443 ssl http2;
        listen [::]:443 ssl http2;

# enable http1.1 support - if module if avaible
#        listen 443 ssl;
#        listen [::]:443 ssl;
 
        root /var/www/html/waste-management-dev/public;

        # Add index.php to the list if you are using PHP
        index index.php;

        server_name unwaste.in;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                #try_files $uri $uri/ =404;
                try_files $uri $uri/ /index.php?q=$uri&$args;

        }

        # pass PHP scripts to FastCGI server
        #
        location ~ \.php$ {
                  try_files $uri =404;
             fastcgi_split_path_info ^(.+\.php)(/.+)$;
             include fastcgi_params;
             fastcgi_pass unix:/run/php/php7.4-fpm.sock;
             fastcgi_index index.php;
             fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
             #fastcgi_param SCRIPT_NAME $fastcgi_script_name;
             #include fastcgi_params;
        }

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


    ssl_certificate /etc/letsencrypt/live/unwaste.in/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/unwaste.in/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}

#EOF

/etc/nginx/sites-enabled는 여러 파일을 사용할 수 있으므로 그렇게 해야 하며 nginx.conf를 건드리지 마십시오. Ubuntu 및 Co와 같은 대부분의 데비안 기반 시스템은 동일한 동작을 합니다.

파일이 로드되지 않으면 nginx 끝에서 다음을 수행해야 합니다.

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

그리고 반대표 대신 먼저 토론해 주세요. 감사합니다;)