Web socket fails to connect through Apache

[lplassman]

OS/Web Information

• Web Browser: Chrome
• Local OS: MacOS 12.2
• Remote OS: Ubuntu 20.04 LTS
• Remote Architecture: amd64
• code-server --version: 4.0.1

Logs

code-server --log debug
[2022-01-11T03:38:43.612Z] info code-server 4.0.1 735c6da
[2022-01-11T03:38:43.613Z] info Using user-data-dir ~/.local/share/code-server
[2022-01-11T03:38:43.628Z] info Using config file ~/.config/code-server/config.yaml
[2022-01-11T03:38:43.628Z] info HTTP server listening on http://0.0.0.0:8080/
[2022-01-11T03:38:43.628Z] info - Authentication is enabled
[2022-01-11T03:38:43.628Z] info - Using password from ~/.config/code-server/config.yaml
[2022-01-11T03:38:43.628Z] info - Not serving HTTPS
[22:38:51] Extension host agent started.
[22:38:51] [Theme Service] Scanning for theme extension...
[22:38:51] [Theme Service] theme-abyss
[22:38:51] [Theme Service] theme-defaults
[22:38:51] [Theme Service] theme-kimbie-dark
[22:38:51] [Theme Service] theme-monokai
[22:38:51] [Theme Service] theme-monokai-dimmed
[22:38:51] [Theme Service] theme-quietlight
[22:38:51] [Theme Service] theme-red
[22:38:51] [Theme Service] theme-solarized-dark
[22:38:51] [Theme Service] theme-solarized-light
[22:38:51] [Theme Service] theme-tomorrow-night-blue
[22:38:51] [Theme Service] Attempting to find user's active theme: Default Dark+
[2022-01-11T03:38:54.949Z] debug got latest version {"latest":"4.0.1"}
[2022-01-11T03:38:54.949Z] debug comparing versions {"current":"4.0.1","latest":"4.0.1"}
[2022-01-11T03:39:51.007Z] debug 0 active connections

Screenshot

Notes

I currently only experience this error on code-server 4.0.1. code-server 3.12.0 works without issue.
I am currently using apache2 with a reverse proxy. The current config for the apache2 virtual host is below:

<Location "/">
ProxyPass http://127.0.0.1:8080/
ProxyPassReverse http://127.0.0.1:8080/
ProxyPassReverse /
RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule ^/?(.*) "ws://127.0.0.1:8080/" [P,L]

I also made sure all the websockets modules are loaded in apache2 and working without problems. No errors occur on the Apache web server. Any suggestions on how to get this working with Apache2?

This issue can be reproduced in VS Code: No

[JimmyNi]

Same issue here. Using apache2 with reverse proxy. Only occur with 4.0.1, code-server 3.12.0 works fine for me.

[jsjoeio]

@code-asher any ideas?

[code-asher]

If the exact same config works with 3.12 that does seem like it could be an issue with 4.0 but I have no idea how; so far all the 1006 errors I have seen have been caused by misconfiguration. I am not very familiar with Apache but maybe this comment has a clue: #2104 (comment)

[konni]

Same issue here using apache2 with reverse proxy

[jamieshaw]

Ditto.

3.12.0 works fine. 4.0.1 returns 1006.
apache2 reverse proxy.

[wombatinua]

Same issue.

[gmiscione]

Same issue, 3.12.0 works fine and 4.0.1 fails with this error. I'm using apache2 as a reverse proxy. Trying to access the service directly without the proxy seems to work

[code-asher]

Sounds like we need to spin up Apache and try to reproduce.

[dokastho]

I found a fix on nginx #4763 not sure if there’s an Apache analog for those settings

[siklosi]

I'm guessing that line from release log "Web socket compression has been made the default (when supported). This means
the --enable flag will no longer take permessage-deflate as an option" is causing problem. I tried finding analog to "proxy_set_header Accept-Encoding gzip" nginx but I have not yet figured way to make it work.

[KaKi87]

not sure if there’s an Apache analog for those settings

Me neither.

the --enable flag will no longer take permessage-deflate

I cannot find any documentation on said flag, how does it work ?
Would there be a --disable flag too, which would allow apache users to upgrade to 4.x ?

[code-asher]

There is no way to disable compression support. It is only used if the browser tells the server that it supports compression. I am not sure issues with compression could cause a 1006 but you could could try stripping `permessage-deflate` from the `Sec-WebSocket-Extensions` header to see if that does anything (this header is how the browser informs the server it supports compression)