Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-2899

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

    XMLWordPrintable

Details

    • Workaround Exists
    • Hide

      (Rephrased in case we have to use this as a KI entry...

      1. For a given workspace like https://devspaces-openshift-workspaces.apps.yourclusterhere/dashboard/#/ide/usernamehere-devspaces/workspacenamehere ...
      2. Open a browser tab to https://devspaces-openshift-workspaces.apps.yourclusterhere/dashboard/
      3. Locate the workspace in the left panel, or from the Workspaces page
      4. Note: if workspace is created via factory, generated name may differ from the Git project name or devfile settings.
      5. Restart the workspace
      Show
      (Rephrased in case we have to use this as a KI entry... For a given workspace like https://devspaces-openshift-workspaces.apps.yourclusterhere/dashboard/#/ide/usernamehere-devspaces/workspacenamehere ... Open a browser tab to https://devspaces-openshift-workspaces.apps.yourclusterhere/dashboard/ Locate the workspace in the left panel, or from the Workspaces page Note: if workspace is created via factory, generated name may differ from the Git project name or devfile settings. Restart the workspace
    • Hide
      = *503 Service Unavailable* or *504 Gateway Time-out* errors

      Currently, you might encounter a *503 Service Unavailable* or *504 Gateway Time-out* error message after refreshing the page of a stopped workspace.

      Workaround: Restart the workspace from the dashboard.
      Show
      = *503 Service Unavailable* or *504 Gateway Time-out* errors Currently, you might encounter a *503 Service Unavailable* or *504 Gateway Time-out* error message after refreshing the page of a stopped workspace. Workaround: Restart the workspace from the dashboard.
    • Documented as Known Issue

    Description

      There was white page with error message "504 Gateway Time-out" after refresh of workspace page, which had gone offline:

      Expected behavior

      workspace to be started again in the same tab, like it was in CRW 2.x

       

      Attachments

        Issue Links

          Activity

            People

              dakwon@redhat.com David Kwon
              dnochevn Dmytro Nochevnov
              Max Leonov Max Leonov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: