Skip to content
Discussion options

You must be logged in to vote

that’s good to hear! What was the misconfiguration? Maybe my issue is the same cause

Hello, this is my modified nginx configuration file. The sections commented out with "new add" are configuration sections added during the fix. Since this was an AI-driven fix, I'm not sure which section specifically took effect. You can compare it with your original configuration file.

# new add
map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

server {
    server_name wall.ex.com; 
    
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/wall.ex.com/fullchain.pem; # managed by Certbot 
    ssl_certificate_key /etc/letsencrypt/live/wall.ex…

Replies: 3 comments 11 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
5 replies
@ildyria
Comment options

@ildyria
Comment options

@CobreDev
Comment options

@ildyria
Comment options

@CobreDev
Comment options

Comment options

You must be logged in to vote
6 replies
@jiaope
Comment options

@CobreDev
Comment options

@ildyria
Comment options

@jiaope
Comment options

Answer selected by ildyria
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Bugs
Labels
Nginx Nginx related problems
3 participants