v4.10.1 #6052
Replies: 5 comments 6 replies
-
For anyone using nginx as a reverse proxy, here is the exact line you need to add to your config. Assumptions:
# /etc/nginx/conf.d/code-server.conf, or wherever you have the reverse proxy config
server {
listen 22222 ssl;
ssl_certificate /etc/ssl/certs/YOUR_CERT_HERE.crt;
ssl_certificate_key /etc/ssl/private/YOUR_KEY_HERE.key;
location / {
proxy_pass http://127.0.0.1:11111;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection upgrade;
+ proxy_set_header Host "your-domain.example.com:22222";
}
} Then reload the config: |
Beta Was this translation helpful? Give feedback.
-
I got exactly the same error. The configuration of my reverse proxy (nginx/swag) hasn't changed. I'm using the linuxserver.io images. The regression happened from |
Beta Was this translation helpful? Give feedback.
-
Anyone has settings for apache? |
Beta Was this translation helpful? Give feedback.
-
same here 4.10.0 works and 4.10.1 does not. pinning to 4.10.0 until this is sorted. |
Beta Was this translation helpful? Give feedback.
-
Might need to use |
Beta Was this translation helpful? Give feedback.
-
Code v1.75.1
Security
Added an origin check to web sockets to prevent cross-site hijacking attacks on
users using older or niche browser that do not support SameSite cookies and
attacks across sub-domains that share the same root domain.
The check requires the host header to be set so if you use a reverse proxy
ensure it forwards that information otherwise web sockets will be blocked.
This discussion was created from the release v4.10.1.
Beta Was this translation helpful? Give feedback.
All reactions