Closed l0rd closed 3 years ago
che-theia needs to use the flattened file now
so while using flattened devfile helps to find endpoints, the issue is the following.
The theia endpoint exposed on DevWorkspaceRouting is using http
but when connecting to this http
endpoint we're redirected to https
Then CheTheia checks if the connections are coming from the endpoint URL but it's not as we're coming from http://..
traffic while endpoint provided is set to http:///
thus, the websocket is closed.
secure:false is defined in the endpoint definition because secure:true
has been told to not be supported
but then: if secure is kept to false:
And while secure:false
is set, we're still redirected from http to https automatically
so it does not work either when using the direct link to the IDE
Testing @metlos tips of using secure: false
but adding the s
suffix on the protocol work
I'll update plug-in registry to provide this mode.
terminal and che-theia now load successfully closing
Describe the bug
When I try to start a workspace (using a factory link that points to a devfile v2.0.0) Theia never loads in my browser.
I am seeing a few errors as shown in the image above.
On the
DevWorkspace
side everything seems to be ok:Talking with @benoitf that looked to be related to the fact that Che Theia is expecting the components endpoints spec to be in the DW whereas that's in the DWT now. The DW only has a reference to a plugin.
Che version
Nightly
Steps to reproduce
Deploy Che, on OpenShift, with devworkspace support enabled
Open a factory link
Runtime
OpenShift 4.7.1
Installation method
Environment
OpenShift dev cluster
Other information
Full
DevWorkspace
spec and status:DevWorkspaceRouting
Che Theia logs
If I try to open the Theia IDE URL I have the following