some resources are 404, work with nginx and docker

[JZLeung]

• Web Browser: Chrome
• Local OS: macOS
• Remote OS: centos8
• Remote Architecture:
• code-server --version: 3.4.1

Docker command

docker run -it -p 127.0.0.1:8080:8080 --name codeserver -v "$PWD:/home/coder/project" -u "$(id -u):$(id -g)" codercom/code-server:latest

Nginx configurations

server {
    listen      80;
    listen      [::]:80;
    server_name example.com

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


    # favicon.ico
location = /favicon.ico {
    log_not_found off;
    access_log    off;
}

# robots.txt
location = /robots.txt {
    log_not_found off;
    access_log    off;
}

# gzip
gzip            on;
gzip_vary       on;
gzip_proxied    any;
gzip_comp_level 6;
gzip_types      text/plain text/css text/xml application/json application/javascript application/rss+xml application/atom+xml image/svg+xml;
}

Docker Logs

info  Wrote default config file to ~/.config/code-server/config.yaml
info  Using config file ~/.config/code-server/config.yaml
info  Using user-data-dir ~/.local/share/code-server
info  code-server 3.4.1 48f7c2724827e526eeaa6c2c151c520f48a61259
info  HTTP server listening on http://0.0.0.0:8080
info      - Using password from ~/.config/code-server/config.yaml
info      - To disable use `--auth none`
info    - Not serving HTTPS

Result

all resources from /lib/vscode/out/vs/base/common/ are 404.

[martinussuherman]

@JZLeung you need to proxy the websocket connection to your container.
workbench.web.api.js needs to use websocket, in your case it's failed.

Use the snippet below as your reference. Note that this is for https connection.

server 
{
    listen       443 ssl http2;
    listen       [::]:443 ssl http2;
    server_name  your.domain.com;

    ssl_certificate         /etc/nginx/ssl-certificate/your.domain.com.pem;
    ssl_certificate_key     /etc/nginx/ssl-certificate/your.domain.com.key;

    root                 /var/www/your.domain.com/;
    index                index.html;
    autoindex            off;

    location / 
    {
        try_files /nonexistent @$http_upgrade;
    }

    location @websocket 
	 {
        # websocket related stuff
        set                  $vscode 127.0.0.1:8080;
        proxy_pass           http://$vscode;    
        proxy_http_version   1.1;
        proxy_set_header     Upgrade $http_upgrade;
        proxy_set_header     Host $host;
        proxy_set_header     X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header     X-Forwarded-Proto $scheme;
        proxy_set_header     Connection "Upgrade";
        proxy_cache_bypass   $http_upgrade;
    }

    location @ 
	 {
        # web related stuff
        set                  $vscode 127.0.0.1:8080;
        proxy_pass           http://$vscode;    
        proxy_http_version   1.1;
        proxy_set_header     Upgrade $http_upgrade;
        proxy_set_header     Host $host;
        proxy_set_header     X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header     X-Forwarded-Proto $scheme;
        proxy_set_header     Connection keep-alive;
        proxy_cache_bypass   $http_upgrade;
    }

Hope this helps.

Regards, Martinus

[20v100]

@martinussuherman Thanks for this snippet. I'm now able to run code-server with Docker behind Nginx proxy. I'm a new to Nginx and cannot change the path as follows:

    location /code/
    {
        try_files /nonexistent @$http_upgrade;
    }

How can I specify that I will access code-server to the URI .../code/ ?

[martinussuherman]

I haven't try this, but maybe you could use the idea from here. The idea is to add rewrite inside the @websocket and @ location blocks, before passing it to the backend. Hope that helps.

Regards,

Martinus

[code-asher]

Does VS Code still work properly? The 404s all look like files that normally only load during development. Did you ever run a development build of code-server? Clearing the cache might resolve the errors.