Blank Page after Login with HTTPS #1122

Activity

1. s94285

   added

   bugSomething isn't workingSomething isn't working

   on Oct 28, 2019
2. sr229 commented on Oct 29, 2019

   

   sr229

   on Oct 29, 2019

   Contributor

   More actions

   I can't confirm this, is this WSL1 or WSL2?
3. sr229

   added

   question

   and removed

   bugSomething isn't workingSomething isn't working

   on Oct 29, 2019
4. s94285 commented on Oct 29, 2019

   

   s94285

   on Oct 29, 2019

   Author

   More actions

   @sr229 Thanks for replying.
   It's on WSL1. I'll try WSL2 later.
5. s94285 commented on Oct 29, 2019

   

   s94285

   on Oct 29, 2019

   Author

   More actions

   @sr229 I'd like to try WSL2 but it is incompatible with vmware.
   So I'll just stick to WSL1. If the problem is caused by WSL1, I'll run it on virtual machine. Thanks.
6. s94285 commented on Oct 29, 2019

   

   s94285

   on Oct 29, 2019

   Author

   More actions

   @sr229 Here's the error that shows on chrome's console:
   Uncaught TypeError: Cannot read property 'hasPendingUpdate' of undefined at p.get hasPendingUpdate [as hasPendingUpdate] (workbench.web.api.js:sourcemap:1627) at workbench.web.api.js:sourcemap:1627
   Then reconnect loop started. Each retry get this error:
   workbench.web.api.js:sourcemap:1605 WebSocket connection to 'wss://s94285vscode.ddns.net/?reconnectionToken=efd1aceb-a767-4e75-af4c-5fb90c4f92e0&reconnection=true&skipWebSocketFrames=false' failed: WebSocket opening handshake timed out
7. code-asher commented on Oct 29, 2019

   

   code-asher

   on Oct 29, 2019

   Last edited by code-asher

   Member

   More actions

   The biggest difference between HTTPS and HTTP is that code-server has to create a proxy socket which is then passed to the extension host (since TLS sockets cannot be passed to other processes). This uses net.createServer and net.connect on ${os.tmpdir()}/code-server/tls-proxy.

   I'm not very familiar with WSL but maybe it has something to do with that.
8. sr229 commented on Oct 29, 2019

   

   sr229

   on Oct 29, 2019

   Contributor

   More actions

   I think this is something to do with WSL1's networking AFAIK, WSL2 uses a virtual switch which should handle HTTPS properly. This may be a WSL issue.
9. Shadowist commented on Nov 2, 2019

   

   Shadowist

   on Nov 2, 2019

   Last edited by Shadowist

   More actions

   I get the same with Safari in iPadOS 13.2 (17B84) now. However, Safari in macOS 10.15.1 works okay in my network.

   Edit: http works okay as well.

   👍React with 👍1Reacted by BossaGroove
11. code-asher commented on Nov 4, 2019

    

    code-asher

    on Nov 4, 2019

    Last edited by code-asher

    Member

    More actions

    Ah you can ignore the 80 in that message. You should be able to see the real connection endpoint in the network tab. VS Code tries to connect over a port and we override it to use the current URL but it's not updated in that message.
12. nhooyr commented on Jan 29, 2020

    

    nhooyr

    on Jan 29, 2020

    Contributor

    More actions

    If this is still a problem, please feel free to reopen.
13. nhooyr

    closed this as completedon Jan 29, 2020
14. clsx524 commented on Feb 2, 2020

    

    clsx524

    on Feb 2, 2020

    More actions

    i still see the same issue. I installed it with traefik to provide SSL on Ubuntu 19.10. Code server is running in docker with http (I did not provide the cert, instead, it’s installed with traefik). I am only able to use it on my Mac with chrome. I tried on safari (mac), safari (iOS 13.3.1), chrome (iOS 13.3.1) but they all got blank page and same error “WebSocket close with status code 1006“ as above.

    Traefik.toml (ver. 1.7.20)

    defaultEntryPoints = ["http", "https"]
    
    [entryPoints]
      [entryPoints.http]
      address = ":80"
      compress = true
        [entryPoints.http.redirect]
        entryPoint = "https"
    
      [entryPoints.https]
      address = ":443"
        [entryPoints.https.tls]
          [entryPoints.https.tls.ClientCA]
            optional = true
          [[entryPoints.https.tls.certificates]]
            certFile = "/etc/traefik/certs/my.cert"
            keyFile = "/etc/traefik/certs/my.key"
    
      [entryPoints.traefik]
      address = ":8083"
    
    

    Labels for code server

          traefik.backend: "code"
          traefik.frontend.rule: "Host:code.domain.com"
          traefik.enable: "true"
          traefik.port: "8080"
    
15. nhooyr commented on Feb 2, 2020

    

    nhooyr

    on Feb 2, 2020

    Contributor

    More actions

    Not working with iOS is expected since you need a non self signed certificate but are you sure it's not working with Safari on Mac? You should see a screen explaining the situation and then you can override and connect.
16. clsx524 commented on Feb 3, 2020

    

    clsx524

    on Feb 3, 2020

    More actions

    Not working with iOS is expected since you need a non self signed certificate but are you sure it's not working with Safari on Mac? You should see a screen explaining the situation and then you can override and connect.

    Is there any way to get non self signed certificate for my local code server in a docker instance? I tried letsencrypt, but it does not take local IP address and unverified domain.
17. clsx524 commented on Feb 9, 2020

    

    clsx524

    on Feb 9, 2020

    More actions

    i still see the same issue. I installed it with traefik to provide SSL on Ubuntu 19.10. Code server is running in docker with http (I did not provide the cert, instead, it’s installed with traefik). I am only able to use it on my Mac with chrome. I tried on safari (mac), safari (iOS 13.3.1), chrome (iOS 13.3.1) but they all got blank page and same error “WebSocket close with status code 1006“ as above.

    Traefik.toml (ver. 1.7.20)

    defaultEntryPoints = ["http", "https"]
    
    [entryPoints]
      [entryPoints.http]
      address = ":80"
      compress = true
        [entryPoints.http.redirect]
        entryPoint = "https"
    
      [entryPoints.https]
      address = ":443"
        [entryPoints.https.tls]
          [entryPoints.https.tls.ClientCA]
            optional = true
          [[entryPoints.https.tls.certificates]]
            certFile = "/etc/traefik/certs/my.cert"
            keyFile = "/etc/traefik/certs/my.key"
    
      [entryPoints.traefik]
      address = ":8083"
    

    Labels for code server

          traefik.backend: "code"
          traefik.frontend.rule: "Host:code.domain.com"
          traefik.enable: "true"
          traefik.port: "8080"
    

    Figured out. My solution is not related to code server but still documented here for future reference

    1. in traefik config, TLS can set to minimum 1.3 but I have to make sure no cypher suites are provided. Incompatible cypher suites would result in errors.
    2. on cloudflare, TLS version should be set to 1.2 minimum, instead of 1.3 minimum. In this way, safari would be as least able to log wss failure, error code 401. The request is still sent with TLS 1.3 but I don't know why this config would matter (chrome does not have this problem).
    3. for the error code 401, I have to disable basic auth in traefik because the authorization code is not part of the request in safari, resulting in 401. However, Chrome would be able to send authorization code. In the end, I use the authorization built with code server.
18. frederickbeaulieu commented on Jun 3, 2020

    

    frederickbeaulieu

    on Jun 3, 2020

    More actions

    Had the same problem with Synology Reverse Proxy.

    Had to set the Proxy Http version to 1.0 in Advanced Settings
19. long-ris3 commented on Jun 29, 2020

    

    long-ris3

    on Jun 29, 2020

    More actions

    Had to set the Proxy Http version to 1.0 in Advanced Settings

    @frederickbeaulieu I still see the blank page after setting the proxy version. Did you do anything else special to make it work on Synology? I set up code-server in a Ubuntu container. It works fine on HTTP without the reverse proxy, but gets stuck at the blank page after login on HTTPS through the proxy. Thanks.
20. frederickbeaulieu commented on Jun 29, 2020

    

    frederickbeaulieu

    on Jun 29, 2020

    More actions

    Here is my config, sorry for the delay, I just moved to a new house and the Syno was not setup yet.

    Docker Image :
    

    https://registry.hub.docker.com/r/linuxserver/code-server/

    Docker config :
    

    Reverse proxy settings :

    

    

    

    👍React with 👍2Reacted by Long Lu and RJ
21. frederickbeaulieu commented on Jun 29, 2020

    

    frederickbeaulieu

    on Jun 29, 2020

    More actions

    @frederickbeaulieu I still see the blank page after setting the proxy version. Did you do anything else special to make it work on Synology? I set up code-server in a Ubuntu container. It works fine on HTTP without the reverse proxy, but gets stuck at the blank page after login on HTTPS through the proxy. Thanks.

    Hope this help
22. long-ris3 commented on Jul 1, 2020

    

    long-ris3

    on Jul 1, 2020

    More actions

    @frederickbeaulieu I still see the blank page after setting the proxy version. Did you do anything else special to make it work on Synology? I set up code-server in a Ubuntu container. It works fine on HTTP without the reverse proxy, but gets stuck at the blank page after login on HTTPS through the proxy. Thanks.

    Hope this help

    Adding the custom headers and ticking the HSTS/HTTP2 boxes in the reverse proxy seem to have done the trick. Thanks!
23. Eternity714 commented on Apr 1, 2021

    

    Eternity714

    on Apr 1, 2021

    More actions

    i still see the same issue，i use docker as the container and use frp to route

    docker-compose.yml

    version: "3.8"
    services:
      frpc:
        image: snowdreamtech/frpc
        volumes:
          - "./frpc.ini:/etc/frp/frpc.ini:ro"
          - "./code.gkotta.cn.crt:/etc/frp/server.crt:ro"
          - "./code.gkotta.cn.key:/etc/frp/server.key:ro"
        restart: unless-stopped
        networks:
          backend:
        environment:
          - "LOCAL_ADDR=code"
          - "LOCAL_PORT=8080"
          - "SUBDOMAIN=code"
      code-server:
        image: codercom/code-server
        ports:
          - "8080:8080"
        volumes:
          - "./data:/home/coder/project"
        environment:
          - "PASSWORD=******"
        restart: unless-stopped
        networks:
          backend:
            aliases:
              - code
    
    networks:
      backend:
    

    frpc.ini

    [common]
    server_addr = x.x.x.x
    server_port = 7000
    
    [code-server]
    type = http
    local_ip = code
    local_port = 8080
    subdomain = code
    
    [code-server-https]
    type = https
    subdomain = code
    
    plugin = https2http
    plugin_local_addr = code:8080
    
    # HTTPS 证书相关的配置
    plugin_crt_path = /etc/frp/server.crt
    plugin_key_path = /etc/frp/server.key
    plugin_host_header_rewrite = 127.0.0.1
    plugin_header_X-From-Where = frp
    
24. jsjoeio commented on Apr 1, 2021

    

    jsjoeio

    on Apr 1, 2021

    Contributor

    More actions

    Hi @Eternity714 - if you're seeing issues, please open a new bug report ticket and fill out the template. That'll help us help you faster! Thanks!