= *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.
(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
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