-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Gitpod stuck in starting a workspace screen infinitely #5401
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 observed this in a system that did have #5300 |
/team workspace |
/schedule |
@csweichel: Issue scheduled in the workspace team (WIP: 0) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
should be fixed by #5449 |
This issue seems to happen in my workspace today. It keeps redirecting with a URL starting with "https://gitpod.io/start/?not_found=true#". But in the dashboard, it's still in a running state. |
Hey @NguyenCongVN, please check https://www.gitpodstatus.com/ |
Hello! @axonasif @meysholdt @roboquat I noticed this reproduces on our setup as well, do you guys have any troubleshooting articles or tips on how to avoid this? Basically, it happens every time I try to activate back an environment which has been IDLE for inactivity. It's not happening each and every time, and I am not sure what could be the cause. |
thanks @jwjsystem for the report. We are looking into it. |
I'm also having this issue, it has happen a few times in recent weeks. It occurs when attempting to restart a workspace that went into idle. I can open other workspaces but not the one I was working on. If you do not stop the workspace from attempting to load by stopping it via the dashboard it will lock you out of Gitpod with the following error: "Error: Authorization failed. Please try again. API rate limit exceeded for user ID XXXXX" |
Im facing this issue. I just signed up $9/mo. WTF. |
Asked for a refund. What trash are you people running?? |
It's not even deleting my account. Don't know what's happening with gitpod! |
/schedule |
/team lol |
Bug description
While trying to open/create a workspace the screen went into infinite loop of redirects. The page refreshed automatically and showed the same page everytime.
On inspecting the logs of ws-proxy it was clear that the response from ws-proxy was to redirect. However, the ws pod was already created and running.
ws-proxy logs:
Steps to reproduce
Not reproduceable. Occurs sporadically.
Expected behavior
Gitpod creates a workspace and opens IDE in the browser.
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: