I get a 503 error right after creating a workspace.
See original GitHub issueSummary
-
che version : 7.3.0
-
runtime : kubernetes
-
screenshots
-
my test devfile.yaml
---
apiVersion: 1.0.0
metadata:
generateName: cdr-
components:
-
type: cheEditor
id: cdr/code-server/2.1523-vsc1.38.1
memoryLimit: 1024Mi
I registered the code-server(Editor) with devfile-registry and added a stack. I get a 503 error right after creating a workspace on the stack. But when I refresh the browser, I get a normal vscode screen. I wonder if there is a way to fix it.
Relevant information
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
How to Fix the HTTP Error 503 Service Unavailable - Kinsta
The 503 error in WordPress signifies that your website can't be reached at the present moment because the server in question is unavailable....
Read more >HTTP Error 503 (Service Unavailable) - IONOS
HTTP Error 503 indicates that a web service isn't available (Service Unavailable). What exactly causes this error and how can it be fixed?...
Read more >503 Service unavailable when pulling TFVC code
We have intermittent errors when pulling source code as part of a build pipeline where the build will report a 503 error and...
Read more >How to Fix 503 Service Unavailable Error: 7 Steps That Work
What Is 503 Service Unavailable Error and What Causes It? 7 Steps to Find Root Cause and Resolve the 503 Error: 1. Check...
Read more >503 Service Unavailable while executing an azure function
Hello;. I created an azure function that connects to Power BI service, retrieves logs and saves data in a Storage blob.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That is by design. We need to know endpoint name to ping that has to be running for any case. In our case, this is cheEditor endpoint name. The predefined list you can find in
che.workspace.server.liveness_probes
variable. To handle that problem you have two options.che.workspace.server.liveness_probes
orCHE_WORKSPACE_SERVER_LIVENESS_PROBES
che.workspace.server.liveness_probes=wsagent/http,exec-agent/http,terminal,theia,jupyter,dirigible
https://github.com/eclipse/che-plugin-registry/blob/master/v3/plugins/dirigiblelabs/dirigible/3.4.0/meta.yaml#L15Issues go stale after
180
days of inactivity.lifecycle/stale
issues rot after an additional7
days of inactivity and eventually close.Mark the issue as fresh with
/remove-lifecycle stale
in a new comment.If this issue is safe to close now please do so.
Moderators: Add
lifecycle/frozen
label to avoid stale mode.