Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Various Files Reporting 404
See original GitHub issueOS/Web Information
- Web Browser: Chrome
- Local OS: Windows 10
- Remote OS: Ubuntu Server 20.04
- Remote Architecture: x64
code-server --version: 3.9.3 fe2dc2deb08e378069891b622bb62ad1d261d1b1
Steps to Reproduce
- Install Code-Server
- Having it working for a while
- Try to connect one day, enter password, blank screen.
Expected
Perfectly Functional Server
Actual
Blank Screen
Log + Info
The server is behind an nginx proxy. The server used to be functional, when I go to one of the URLs reported as a 404, I receive: {"error":"ENOENT: no such file or directory, open '/usr/lib/code-server/lib/vscode/out/vs/base/common/lifecycle.js'"}. I have checked the folder it is looking for, and it indeed does not contain those files. Issue #1640 seems to have a similar issue, yet was fixed with an update.
Browser Log: (domain cropped off)
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sorry for the late response, but I can confirm it’s something funky with the proxy. Directly accessing the server works fine. I’ll close this since it’s something on my system.
Oh, or not, http2_protocol_error is causing
workbench.web.api.jsto not load, Chrome just decided in it’s infinite wisdom to not highlight that. Gonna look deeper into my NGINX config