500 error: 3.9.2 not working on Android + Termux

OS/Web Information

• Web Browser: Chrome for Android
• Local OS: Android 9 Pie
• Remote OS: Server? If so, Android 9 Pie on Termux
• Remote Architecture: ARM
• code-server --version: 3.9.2 109d2ce

Steps to Reproduce

1. Install code-server as normal with yarn
2. Start it
3. Log in to localhost:8080

Expected

VSCode would appear

Actual

500 error is displayed on the screen, alongside with the "go home" button which gives the exact same error

Screenshot

20210405_154607.mp4

EDIT: Link above is broken, here is a video showing everything: https://youtu.be/w2MCCDTNfsU

Notes

This issue can be reproduced in VS Code: No

@jsjoeio Sorry for the video delay, I didn't see that it didn't record chrome, then I had to install edge, make a new recording, and also compress it due to GitHub limitations, now it's available

[jsjoeio]

No worries at all! Thanks for opening this up so quickly. I should be able to investigate today.

P.S. the video isn't working on my side. I just see a black screen

No worries at all! Thanks for opening this up so quickly. I should be able to investigate today.

P.S. the video isn't working on my side. I just see a black screen

I'm gonna break somethingLet me try and upload it to YouTube!

https://youtu.be/w2MCCDTNfsU Okay, quality may not be the best because of YouTube, it should be at full res soon

EDIT: Gonna edit it too in the issue

[jsjoeio]

That worked! Hmm...so strange. Okay, let me try to reproduce locally on my Android.

[jsjoeio]

Well, I have good news and bad news.

Good News

I was able to successfully reproduce this on my Pixel 2 in both Chrome and Firefox.
https://user-images.githubusercontent.com/3806031/113616529-115bcb80-960a-11eb-88b8-864f251f520d.mp4

Bad News

Even running with --log debug leads to no hints as to what's wrong.

I'll add this to the next milestone so can investigate further. Thanks for helping us find this.

Suggested Workaround

Use 3.9.1 until we get this fixed.

Damn, so it wasn't some weird thing I did. Well, in that case, shouldn't a temporal warning be made on the repo telling that 3.9.2 isn't working in these devices?

[jsjoeio]

Yes, good idea! I will pin this issue so people see it and I'll make an announcement in Discussions: posted