-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Extremely poor connection for SEA region and CORs error #10920
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We are aware of the latency issues and have plans for improving that #7489. Nonetheless, you shouldn't be experiencing errors. Are those errors only visible in the Chrome Dev Tools console or do you experience any issues? Edit: Moved to IDE inbox given the CORS issues in blobserve. |
It takes a long time for the file explorer to load its file too. |
Hey @kunxin-chor, this CORs error is known Your problem maybe due to latency that @atduarte mentioned above #10920 (comment), but we need to investigate what happened in your workspace, could you provide more information? i.e.
|
Another issues also include the file explorer taking a long time to load, saving files is non-responsive and port 3000 taking a long time to connect. For the logs I will follow up via email. |
Hey @kunxin-chor, thanks for your logs provide 🙏 , I thought the problem you faced might be because of the network problem that atduarte mentioned above #10920 (comment). You can try with VPN to see if it works for you, and we have an issue to add Singapore (sg) region to Gitpod #5534, please upvote 👍 and track it here. Feel free to reopen it if VPN not works for you. |
Bug description
Gitpod's connection has been bad on decent Internet speed (30mbps) for users in SEA region. There are also CORS error and websockets to Gitpod servers take an extremely long time to send response back or will time out.
Steps to reproduce
Open a workspace
Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
The text was updated successfully, but these errors were encountered: