Nginx: 502 Bad Gateway

[kaaax0815]

I did exactly how it was in the Guide
I replaced mydomain.com with code.kaaaxcreators.de

/etc/nginx/sites-enabled

server {
    server_name code.kaaaxcreators.de;

    location / {
      proxy_pass http://localhost:8080/;
      proxy_set_header Host $host;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection upgrade;
      proxy_set_header Accept-Encoding gzip;
    }

    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/code.kaaaxcreators.de/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/code.kaaaxcreators.de/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

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


    listen 80;
    listen [::]:80;
    server_name code.kaaaxcreators.de;
    return 404; # managed by Certbot


}

sudo certbot --non-interactive --redirect --agree-tos --nginx -d code.kaaaxcreators.de -m <email>

Code Server is running as Service when running it again it says error listen EADDRINUSE: address already in use 127.0.0.1:8080, which makes sense

NGINX Error Log:

2021/01/18 13:45:28 [error] 235#235: *40 connect() failed (111: Connection refused) while connecting to upstream, client: 2003:db:8f06:9800:e953:17a2:8b5d:1a95, server: code.kaaaxcreators.de, request: "GET / HTTP/1.1", upstream: "http://[::1]:8080/", host: "code.kaaaxcreators.de"
2021/01/18 13:45:28 [error] 235#235: *40 connect() failed (111: Connection refused) while connecting to upstream, client: 2003:db:8f06:9800:e953:17a2:8b5d:1a95, server: code.kaaaxcreators.de, request: "GET /favicon.ico HTTP/1.1", upstream: "http://[::1]:8080/favicon.ico", host: "code.kaaaxcreators.de", referrer: "https://code.kaaaxcreators.de/"
2021/01/18 13:45:30 [error] 235#235: *40 connect() failed (111: Connection refused) while connecting to upstream, client: 2003:db:8f06:9800:e953:17a2:8b5d:1a95, server: code.kaaaxcreators.de, request: "GET /static/c4610f7829701aadb045d450013b84491c30580d/usr/lib/code-server/dist/serviceWorker.js HTTP/1.1", upstream: "http://[::1]:8080/static/c4610f7829701aadb045d450013b84491c30580d/usr/lib/code-server/dist/serviceWorker.js", host: "code.kaaaxcreators.de", referrer: "https://code.kaaaxcreators.de/static/c4610f7829701aadb045d450013b84491c30580d/usr/lib/code-server/dist/serviceWorker.js"
2021/01/18 13:46:46 [notice] 638#638: signal process started
2021/01/18 13:46:47 [notice] 647#647: signal process started
2021/01/18 13:47:02 [notice] 663#663: signal process started
2021/01/18 13:47:05 [notice] 672#672: signal process started

I use NGINX over Caddy because of this: #2585

But because I have a different service running too, it is bad to stay with an error. Maybe you find a simple solution, I will use this, otherwise I will go back to Caddy and use it with --link and a redirect

[code-asher]

"Connection refused" makes it look like code-server isn't actually running. You might want to double-check what's running on port 8080, for example with netstat -tulpn.