Nginx not redirecting correctly on fresh local install

[coatmaker618]

Tried to follow the installation on this github page and I was able to get code-server installed, but I cannot get nginx to point to it successfully!

Background: I am selfhosting this service on it's own VM. After following the instructions on this github page I was able to navigate to the code-server http URL. However, the prescribed nginx code gives me a 502 (bad gateway) rather than the desired page. Before deleting the default nginx page (not listed in instructions), I DID get the "welcome to nginx" page, so it would seem nginx is installed correctly. I'm sure it's something simple, and yes, I did change the URL in "server_name".

Any advice would be appreciated, and once i get this running, I'd be happy to update the docs for a self-hosted instructions if desired.

Reporting Disclaimer: This may be fixed with a documentation change, but as it's preventing VSCode from being usable, I'm currently considering it a bug.

[jsjoeio]

Hey @coamtaker618 - thanks for the extra details in the issue and sorry to hear you're having trouble!

Apologies, I have not set code-server up manually with nginx. Have you already looked through nginx-related discussions?

Here are two that seem directly related to the issue you're running into:

• NGINX 502 Bad Request suddenly without changing anything? #2607
• Nginx: 502 Bad Gateway #2593

[balajib-b]

I have been using the nginx with SSL successfully for almost an year. @coamtaker618 could you please try the below nginx settings and let us know.

`server {

server_name **EXAMPLE.COM**;

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

}`

@jsjoeio requesting you to test and confirm it.

[jsjoeio]

Thanks chimming in @balajib-b! 🙌 Added this to the current milestone. Hoping I can find time to try it myself and see if it works.

[coatmaker618]

Still no luck :( See below for my nginx page. The only thing I changed after copy/paste is my server URL

I had a line " listen 80;" but got rid of that since you didn't have it. Didn't seem to make a difference. If I navigate to 8080 directly, it seems to work fine (I get a login prompt & vscode when I login)--but navigating to port 80 I still get a 502 (Bad Gateway). And I did make sure to restart nginx after changing the file :)

server {
    server_name code.mydomain;

    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;
    }
}

[coatmaker618]

@jsjoeio I did try searching for NGINX issues with code-server but I certainly could have missed something!

#2593 may be exactly my problem but there was no further communication from poster, and the recommended suggestion was "check if code-server" is actually running. Certainly good advice, but I know it is because I can get to it on port 8080.

#2607 seems like a more complex setup, but also no further communication from the OP :( The nginx setup seems to be more complicated than mine, and so most of the advice doesn't apply. That said, I'd be happy to check nginx logs if I knew how >_<

[balajib-b]

@coamtaker618 you are accessing code server using associated domain name or using IP address.

@jsjoeio there had been a discussion on another thread about the one click deployment to clouds. I am willing to help regarding cloud deployment. Let me know your interest and support from your side.

[coatmaker618]

@balajib-b I'm using a domain (strictly a subdomain of a domain that I own). I have a few other services I'm hosting so I don't think the problem is a bad domain, but it never hurts to check!

[coatmaker618]

Email sent

[jsjoeio]

Sorry to hear that didn't help much @coamtaker618 - we'll see if we can take a look.

@balajib-b regarding the one-click deployments - thanks for offering some help! @bpmct was leading the effort and actually merged a PR yesterday: #2843

Feel free to open a new Discussion and tag myself if you have more ideas or want to get more involved!

[martinussuherman]

@coatmaker618

Try change this:

proxy_pass http://localhost:8080/;

to this:

proxy_pass http://localhost:8080;

and see if that works.

Regards,

Martinus

[coatmaker618]

@martinussuherman gave that a try & no change. But thanks for the suggestion!