[Bug]: The workbench failed to connect to the server #6014

Activity

1. JonSmall

   added

   bugSomething isn't workingSomething isn't working

   triageThis issue needs to be triaged by a maintainerThis issue needs to be triaged by a maintainer

   on Feb 11, 2023
2. code-asher commented on Feb 13, 2023

   

   code-asher

   on Feb 13, 2023 via email

   Member

   More actions

   Does the IP you are connecting to go directly to the Docker container or is there some kind of proxy in between? Usually 1006 means something is dropping the web socket. Is this Docker Desktop on Windows or over WSL?
3. ManuXD32 commented on Mar 29, 2023

   

   ManuXD32

   on Mar 29, 2023

   More actions

   Does the IP you are connecting to go directly to the Docker container or is there some kind of proxy in between? Usually 1006 means something is dropping the web socket. Is this Docker Desktop on Windows or over WSL?

   I am having the same error, mine is through an apache reverse proxy. I have tried the solutions of other threads, but they just don't work.
   Any idea?
4. code-asher commented on Mar 30, 2023

   

   code-asher

   on Mar 30, 2023 via email

   Member

   More actions

   Do you see any warnings or errors in code-server's logs? If you are using 4.10.1 or later also make sure that the host header matches the origin header that the browser is sending otherwise the socket will be blocked for security reasons.
5. ManuXD32 commented on Apr 5, 2023

   

   ManuXD32

   on Apr 5, 2023

   More actions

   Do you see any warnings or errors in code-server's logs? If you are using 4.10.1 or later also make sure that the host header matches the origin header that the browser is sending otherwise the socket will be blocked for security reasons.

   It turned out to be a missconfiguration under the .conf file. GPT4 solved It heh. Thank you so much, anyway.

   👍React with 👍1Reacted by Asher
6. freaker2112 commented on Apr 11, 2023

   

   freaker2112

   on Apr 11, 2023

   More actions

   Do you see any warnings or errors in code-server's logs? If you are using 4.10.1 or later also make sure that the host header matches the origin header that the browser is sending otherwise the socket will be blocked for security reasons.

   It turned out to be a missconfiguration under the .conf file. GPT4 solved It heh. Thank you so much, anyway.

   what fixed it? I'm having this same issue
7. ManuXD32 commented on Apr 20, 2023

   

   ManuXD32

   on Apr 20, 2023

   Last edited by ManuXD32

   More actions

   Do you see any warnings or errors in code-server's logs? If you are using 4.10.1 or later also make sure that the host header matches the origin header that the browser is sending otherwise the socket will be blocked for security reasons.

   It turned out to be a missconfiguration under the .conf file. GPT4 solved It heh. Thank you so much, anyway.

   what fixed it? I'm having this same issue

   Try changing your .conf file to look like this: Ps: remember to end the conf file with "</VirtualHost>" for some reason my comment looks weird,

   <VirtualHost *:80>
   ServerName codeYOUR_DOMAIN
   ServerAdmin USER@YOUR_DOMAIN
   ProxyPreserveHost On
   ProxyRequests Off
   AllowEncodedSlashes NoDecode

   <Location />
       ProxyPass http://localhost:YOUR_PORT/ nocanon
       ProxyPassReverse http://localhost:YOUR_PORT/
       ProxyPassReverseCookieDomain localhost codeYOUR_DOMAIN
       ProxyPassReverseCookiePath / /
   </Location>
   
   RewriteEngine On
   RewriteCond %{HTTP:Upgrade} websocket [NC]
   RewriteCond %{HTTP:Connection} upgrade [NC]
   RewriteRule ^/?(.*) "ws://localhost:YOUR_PORT/$1" [P,L]
   
   ErrorLog ${APACHE_LOG_DIR}/error.log
   CustomLog ${APACHE_LOG_DIR}/access.log combined
   

   </VirtualHost>
8. code-asher commented on Jul 12, 2024

   

   code-asher

   on Jul 12, 2024

   Member

   More actions

   Closing as stale but feel free to comment if you come back to this.
9. code-asher

   closed this as not plannedon Jul 12, 2024