Skip to content
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

Workspace fails to start/open. Caused by Unknown error during websocket connection establishing #14726

Closed
mmorhun opened this issue Oct 1, 2019 · 9 comments · Fixed by #15516
Assignees
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.

Comments

@mmorhun
Copy link
Contributor

mmorhun commented Oct 1, 2019

Describe the bug

When try to open/start a workspace, it fails with Unknown error has happened, try to reload page message. Reload of the page doesn't help.

Che version

nightly

Steps to reproduce

  1. Open a workspace
  2. Work in it some time
  3. Stop the workspace
  4. Try to start it again

Expected behavior

Workspace is started as usual

Runtime

minishift

Screenshots

unknown-error

Screen cast

unknown-error

Additional context

No error logs on Che master side.

@mmorhun mmorhun added kind/bug Outline of a bug - must adhere to the bug report template. area/dashboard labels Oct 1, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Oct 1, 2019
@akurinnoy
Copy link
Contributor

@mmorhun, I have just faced same issue on minikube on single-user Che.

@mmorhun
Copy link
Contributor Author

mmorhun commented Oct 1, 2019

Yes, seems keycloak token is not the problem, because relogin didn't help...
But closing and opening browser again helped.

@sleshchenko
Copy link
Member

Something is wrong in cookies or local cache since the incognito window helped in @akurinnoy case.

@l0rd l0rd added team/ide2 severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 1, 2019
@l0rd
Copy link
Contributor

l0rd commented Oct 1, 2019

@evidolob @olexii4 @benoitf any idea? Is this a regression?

@l0rd l0rd changed the title Unknown error on workspace start Unknown error on workspace re-start Oct 1, 2019
@olexii4
Copy link
Contributor

olexii4 commented Oct 3, 2019

@mmorhun, I have the same issue on minikube on single-user CHE.
I tried to clean cookies and local cache - didn't help.

@sleshchenko sleshchenko changed the title Unknown error on workspace re-start Workspace fails to start/open. Caused by Unknown error during websocket connection establishing Oct 7, 2019
@evidolob
Copy link
Contributor

evidolob commented Oct 7, 2019

I faced same problem with Che-Theia IDE, for some reasons browser cannot establish websocket connection with Theia backend. See screenshot:
Screen Shot 2019-10-07 at 14 18 52

@AndrienkoAleksandr
Copy link
Contributor

+1 Faced with this issue.

@tsmaeder
Copy link
Contributor

I might have filed a duplicate: #15041

@l0rd
Copy link
Contributor

l0rd commented Oct 31, 2019

If it can help I've faced this issue as well and when I've switched into chrome incognito mode and I could start the workspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
9 participants