"Cannot reconnect. Please reload the window." in Raspberry Pi and over HTTPS

[chilcano]

• Web Browser: Chrome, Firefox, Edge
• Local OS: Windows 10
• Remote OS: Raspbian GNU/Linux 10 (buster)
• Remote Architecture: ARMv7 rev 4 (Raspberry Pi 3b+)
• code-server --version: 3.5.0

I've installed Code-Server 3.5.0 in my Raspberry Pi, it is running over HTTPS using no self-signed certificates.
When I connect from a browser (with root CA already installed) I'm getting inmediatelly the Cannot reconnect. Please reload the window. message and everything doesn't work anymore until I reload the page.

I'm using this bash script to install (NodeJS, NPM, Yarn) Code-Server and during the installation I'm getting this log message.

...
yarn install v1.22.5
info No lockfile found.
[1/4] Resolving packages...
warning @types/[email protected]: This is a stub types definition for applicationinsights (https://github.com/Microsoft/ApplicationInsights-node.js). applicationinsights provides its own type definitions, so you don't need @types/applicationinsights installed!
warning @types/[email protected]: This is a stub types definition. chokidar provides its own type definitions, so you do not need this installed.
warning @types/[email protected]: This is a stub types definition. keytar provides its own type definitions, so you do not need this installed.
warning asar > mksnapshot > [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
warning asar > mksnapshot > request > [email protected]: this library is no longer supported
warning cson-parser > [email protected]: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
warning gulp > glob-watcher > [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
warning gulp > glob-watcher > chokidar > [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning gulp > gulp-cli > matchdep > micromatch > snapdragon > source-map-resolve > [email protected]: Please see https://github.com/lydell/urix#deprecated
warning gulp > gulp-cli > matchdep > micromatch > snapdragon > source-map-resolve > [email protected]: https://github.com/lydell/resolve-url#deprecated
warning gulp-azure-storage > azure-storage > [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
warning gulp-cssnano > cssnano > autoprefixer > [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
warning gulp-cssnano > cssnano > postcss-merge-rules > [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
warning gulp-cssnano > cssnano > postcss-merge-rules > caniuse-api > [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
warning gulp-remote-retry-src > [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
warning jsdom-no-contextify > [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
warning mocha > [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning mocha > glob > [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
warning mocha > [email protected]: to-iso-string has been deprecated, use @segment/to-iso-string instead.
warning mocha > [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade
warning mocha > jade > [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning [email protected]: The package has been renamed to `open`
warning sinon > [email protected]: This package has been deprecated in favour of @sinonjs/samsam
warning sinon > [email protected]: This package is unmaintained. Use @sinonjs/formatio instead
warning sinon > formatio > [email protected]: This package has been deprecated in favour of @sinonjs/samsam
warning webpack > watchpack > watchpack-chokidar2 > [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
[2/4] Fetching packages...
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > @coder/[email protected]" has unmet peer dependency "@google-cloud/logging@^4.5.2".
warning " > [email protected]" has incorrect peer dependency "typescript@^3.0.0".
[4/4] Building fresh packages...
Done in 483.44s.
yarn install v1.22.5
warning package.json: No license field
info No lockfile found.
warning [email protected]: No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
....

If I disable HTTPS and run Code-Server on HTTP (without certificates), Code-Server works.
This issue is similar to this #1884 and #1227, the unique difference it is I'm running on Raspberry Pi armv7 (Buster - 32bits).

Any idea how to fix this problem?.
Regards.

[code-asher]

Could you grab some logs? https://github.com/cdr/code-server/blob/master/doc/FAQ.md#how-do-i-debug-issues-with-code-server

Are you using a reverse proxy or giving these certificates directly to code-server?

[chilcano]

I've added remoteagent log and traces to existing Gist.
Not, I'm not using reverse proxy, I've enabled HTTPS in code-server and configured pub cert/priv key pem files. Below my config.yaml

$ cat ~/.config/code-server/config.yaml

bind-addr: 0.0.0.0:8443
auth: password
password: cd1eb0c8f3ae0689ac9f5875
cert: vscs-rpi.pem
cert-key: vscs-rpi-key.pem
disable-telemetry: true

This similar configuration worked for version 3.4.1
Regards.

[code-asher]

Hmmm, I don't see any indications of a crash so I suppose it must be some kind of issue with the websocket. Do you see any messages in the browser console?

If you drop in 3.4.1 with the same configuration it works?

[chilcano]

If you drop in 3.4.1 with the same configuration it works?

Yes, it works with 3.4.1 version.

I've installed Ubuntu 20.04 64 bits in Raspberry Pi 3 and installed the arm64.deb, but unfortunately that didn't work. I had the same issue if install in Raspbian (32 bits) with NPM/NodeJS/Yarn.

Again, I installed 3.5.0 in Ubuntu 20.04 on an Intel i7 Laptop and configured to expose Code-Server on TLS like above and worked without issues.

Seems some library used in the Raspberry Pi (Rasbian/32 bits or Ubuntu/64 bits) required by TLS is not working properly.
Hope this helps.
Any help is welcome.
Regards.

[code-asher]

Hmm, I'm not sure what it could be, maybe something odd with our build process...we should have 3.5.1 soon so we'll have to test and see if it fares any better.