Error: Failed to get the workspace: "Unknown error"
See original GitHub issueDescribe the bug
I was not able to load my go based workspace.
Che version
- latest
Steps to reproduce
Unknown. I just create a go based workspace and try to start it.
Expected behavior
The workspace should load correctly.
Runtime
- Openshift (include output of
oc version
)
Screenshots
Installation method
- chectl
chectl server:start --platform=crc --installer=operator --os-oauth --tls --self-signed-cert
Environment
- macOS
Additional context
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Troubleshoot issues accessing your WorkSpace from the ...
This error typically indicates that the WorkSpaces client can authenticate over port 443, but can't establish a connection over TCP port 4172.
Read more >Failed to start the workspace: "Unknown error" · Issue #13197
Description Unable to create workspace on che/dashboard. Encountering error : Error: Failed to start the workspace: "Unknown error" ...
Read more >Unable to sign in to workspace: Unknown Error Occurred
Enter credentials > Starting Workspace > Launching Session > Unknown Error Occurred - we couldn't launched your workspace. Please try again.
Read more >Error "Unknown Error" when trying to open Service after ...
This error can occur after applying a Template to the workspace that contains the 'Request Template' selected in the Service; or if a...
Read more >New Build System Error - missingWorkspaceContext
Individual build tasks may have failed for unknown reasons. One possible cause is if there are too many (possibly zombie) processes; in this...
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
No longer reproduced.
@skabashnyuk I’m not able to reproduce this bug anymore. Could you please confirm or deny same on your side?