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.

Sign up for GitHub

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

Jump to bottom

"504 Gateway Time-out" after workspace went offline, and it wasn't clear how to restore workspace #21347

Closed
dmytro-ndp opened this issue Apr 25, 2022 · 4 comments
Closed

"504 Gateway Time-out" after workspace went offline, and it wasn't clear how to restore workspace #21347

dmytro-ndp opened this issue Apr 25, 2022 · 4 comments
Labels
kind/bug Outline of a bug - must adhere to the bug report template. status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github.

Comments

@dmytro-ndp
Copy link
Contributor

Describe the bug

There was "504 Gateway Time-out" after workspace went offline:
Screenshot from 2022-04-22 17-08-32

There was white page with error message "504 Gateway Time-out" after refresh of page.
Screenshot from 2022-04-22 13-03-36

It wasn't clear how to restore

Che version

next (development version)

Steps to reproduce

  1. Go to Eclipse Che dogfooding instance.
  2. Start workspace
  3. Keep workspace tab opened, but do nothing inside workspace tab.
  4. Wait on workspace to go offline
  5. Reload workspace page

Expected behavior

Workspace to be started automatically after refresh, like it was in che-server mode.

Runtime

OpenShift

Screenshots

No response

Installation method

other (please specify in additional context)

Environment

other (please specify in additional context)

Eclipse Che Logs

No response

Additional context

No response
@dmytro-ndp dmytro-ndp added the kind/bug Outline of a bug - must adhere to the bug report template. label Apr 25, 2022
@dmytro-ndp dmytro-ndp changed the title "504 Gateway Time-out" after workspace went offline, and wasn't clear how to restore workspace "504 Gateway Time-out" after workspace went offline, and it wasn't clear how to restore workspace Apr 25, 2022
@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 Apr 25, 2022
@nickboldt
Copy link
Contributor

Similar issue (with 503) in #20599

@dmytro-ndp
Copy link
Contributor Author

@nickboldt : Error 503 != 504.
So, #20599 is about different problem, IMHO

@nickboldt
Copy link
Contributor

nickboldt commented Apr 25, 2022 •
edited
Loading

I'm aware that 503 != 504; my point is that there's apparently a lot of problems related to timeout/inactivity/expired tokens, which impact UX.

"went offline" and "idled for inactivity" sound like the same event to me, but with different words. :D

@dmytro-ndp
Copy link
Contributor Author

Agreed.
I will closed the issue as duplicating.

Thank you for notice, @nickboldt !

@ibuziuk ibuziuk mentioned this issue Apr 26, 2022
Closed
58 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Outline of a bug - must adhere to the bug report template. status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nickboldt @dmytro-ndp @che-bot