Che on a cloud server - Not able to create a workspace #3576
Comments
TylerJewell
added
the
kind/question
|
@pramodak - this indicates that you have a networking configuration issue. The workspace is unable to make a connection back to the Che server, and the Che server is unable to ping the workspace. There are configuration properties that you can alter that will change how workspaces connect back to the Che server. First, we are in the middle of making our 5.0.0 release, so please use the following syntax for running Che: Second, once you run Che with that syntax, it will install a che.env file that has various networking parameters in there that you can configure and then rerun Che. There is descriptions of the variables that you need to set to enable communication between the workspace and the Che server. Please let us know how that goes. |
|
@pramodak can you also share workspace agent logs? Do you have ephemeral port range opened? I suspect that the workspace is up but smth is blocking Che server from reaching it. |
|
Thanks to both Tyler and Eugene for the comments. @eivantsov : I have opened the ephemeral port range (32768-65535 - both TCP/UDP) for the cloud server. I am not sure where to find the correct logs for workspace agent. In the dev-machine container, I see the following log. No errors as such. |
|
@pramodak according to ws agent logs, it is able to reach ws-master but not vice versa. It might be a security (firewall) or networking issue. Is firewall on? |
|
@eivantsov : I see that the ufw is inactive on the server where docker is running. On the project container, ufw is not present. |
|
@pramodak even though you can access CHE at 10.39.89.244 Che server, running in a container, cannot reach a workspace agent that runs on the same host in a different container. Can you try the following? DO NOT export I expect that the workspace will be considered as running, but your browser won't be able to connect to it (expected). If this is the case, then there's some sort of a networking/security issue where connections from one container to another are blocked when 10.39.89.244 is used. FYI, I cannot reproduce this one on a clean Ubuntu launched on Digital Ocean or Amazon. |
|
@TylerJewell @eivantsov I am facing the same issue @pramodak Did the problem fix for you |
|
@TylerJewell that PR addresses a bit different problem. Here in this case server cannot reach ws agent, not client. I suspect this is either blocked port issue since the server uses an external IP to reach ws agent over ephemeral port range or some security restriction that prevents communication between Docker containers (which is unlikely since ws agent CAN reach workspace master) |
|
@eivantsov - RedHat has a pending PR which changes the routing of requests from server->agent and agent->server to use internal IP addresses. But for the life of me that I cannot find it now. Do you know where it is - could it be useful here? |
|
@eivantsov If I do not export CHE_HOST_IP, I get the following error.
And the logs are as below. Let me check if I can fiddle around the network configuration to get it working. |
|
@TylerJewell I think you are talking about PR #3282 that fixes issue #2030 @pramodak tips provided in this comment may be helpful to confirm the nature of your problem |
|
@pramodak can you run a simple test?
Go to Then run:
When inside a container:
Is this command successful for you? If not, then it is security issue with the VM. |
|
@eivantsov The curl command is not successful and there is a timeout error. So, it looks like a security issue with the VM which I need to debug further. |
|
@pramodak - thanks for the investigation persistence. |
|
@pramodak - how did it go? |
|
@pramodak any update please? |
|
Hi @eivantsov @TylerJewell, |
ghost
closed this as 
I am not able to create a workspace (my first workspace) after installing and opening che from the browser (I tried firefox and chrome browsers)
Reproduction Steps:
The cloud server where che is running has the public IP address as "10.39.89.244". I configured CHE_HOST_IP=10.39.89.244 and start che on the cloud server.
When I try creating a new workspace from the Che UI, I see an error as below.
Expected behavior:
The workspace should be created
Observed behavior:
Issue with the workspace creation as mentioned above.
Che version: 5.0.0-latest
OS and version: Ubuntu 16.04 LTS
Docker version: 1.12.5
Che install: Docker container
Additional information:
The stack trace from the docker logs is as below.
The text was updated successfully, but these errors were encountered: