An unexpected error occurred that requires a reload of this page. The workbench failed to connect to the server (Error: Time limit reached)
See original GitHub issueHi there! 👋
I have some issues after deploy code server on kubernetes accessible through a subpath.
OS/Web Information
- Web Browser: Chrome
- Local OS: Centos
- Remote OS:
- Remote Architecture:
code-server --version
: 3.11.1
Steps to Reproduce
- Deploy Code-server on kubernetes
- In Ingress set a subpath to access to code-server
Expected
Actual
Logs
Screenshot
Notes
This issue can be reproduced in VS Code: Yes/No
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Studio Code Server: An unexpected error occurred that ...
An unexpected error occurred that requires a reload of this page. The workbench failed to connect to the server (Error: Time limit reached)....
Read more >vscode remote-ssh cannot connect to server - Stack Overflow
I've been developing locally by connecting to Vagrant (vartualbox) with vscode remote-ssh. But when I restarted vagrant and tried to connect ...
Read more >Troubleshooting Cloud Functions - Google Cloud
Function deployment fails while executing function's global scope. This error indicates that there was a problem with your code. The deployment pipeline ...
Read more >4.5.4 mysqldump — A Database Backup Program
It dumps one or more MySQL databases for backup or transfer to another SQL server. The mysqldump command can also generate output in...
Read more >How to Fix the 504 Gateway Timeout Error on Your Site - Kinsta
To simplify it further, this error occurs when two servers are involved in processing a request. The first server (typically the main server) ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ah I think older versions of code-server used to report the websocket was port 80 even though it really used the current port, so that might be why it looks like it connects to 80.
The websocket URL is not possible to configure at the moment but it is supported in the code.
If port 80 is disabled code-server should not be loading at all should it? code-server uses the same port for the websocket that is used to serve the HTML.