| [che-dev] Eclipse Che through Corporate Firewall |
Hi Folks, I have been looking at Eclipse Che as an alternative to server side code editing with Emacs, Vi and friends. I am using an Ubuntu 18.04 system remotely over ssh, with ports forwarded through the ssh tunnel as required. These are *internal* big iron servers that are not exposed to the internet, accessing them requires traversing a corporate VPN and an isolation firewall that only allows SSH through. So I followed the getting started guide and after a few small snafu's installing docker, and setting up the corporate proxy I managed to get the Eclipse CHE environment installed. My problem is that when I try to create a workspace it times out with the error. Error: Failed to run the workspace: "Server 'wsagent/http' in machine 'dev-machine' not available." You can see the full error in pastebin - https://pastebin.com/RRAMAkd2 Google chrome shows the following error in it's dev console. app-460dc1929e.js:46488 {error: "Server 'wsagent/http' in machine 'dev-machine' not available.", status: "STOPPED", workspaceId: "workspacebgkivl2vug8u5a0k", prevStatus: "STARTING"} (anonymous) @ app-460dc1929e.js:46488 (anonymous) @ app-460dc1929e.js:172256 c @ app-460dc1929e.js:48760 (anonymous) @ app-460dc1929e.js:48776 $eval @ app-460dc1929e.js:50020 $digest @ app-460dc1929e.js:49838 i.safeDigest @ app-460dc1929e.js:125436 t @ app-460dc1929e.js:125436 i._onMessageHandler @ app-460dc1929e.js:125436 workspace-loader.ts:46 Error: Failed to run the workspace: "Server 'wsagent/http' in machine 'dev-machine' not available." at workspace-loader.ts:213 at che-json-rpc-master-api.ts:209 at json-rpc-client.ts:191 at Array.forEach (<anonymous>) at e.processNotification (json-rpc-client.ts:190) at e.processResponse (json-rpc-client.ts:177) at json-rpc-client.ts:94 at websocket-client.ts:115 at Array.forEach (<anonymous>) at e.callHandlers (websocket-client.ts:115) The odd thing is that if I do a 'docker ps' I see the workspace has been created, see eclipse-che/workspace... below. CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d917d4bc9968 eclipse-che/workspacebgkivl2vug8u5a0k_null_che_dev-machine "/home/user/entrypoi…" About a minute ago Up About a minute 22/tcp, 4403/tcp, 0.0.0.0:32806->4401/tcp, 0.0.0.0:32805->4411/tcp, 0.0.0.0:32804->4412/tcp workspacebgkivl2vug8u5a0k_null_che_dev-machine ffea2551a1aa eclipse/che-server:7.0.0-beta-4.0 "/entrypoint.sh" 7 hours ago Up 7 hours 8000/tcp, 0.0.0.0:8080->8080/tcp che If I open a shell in that workspace I see a bunch of java processes, which I assume is what the browser is waiting to hear from? See this pastebin for more ... https://pastebin.com/vXB4GRkH. root@silpixa00395806:~# docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock -v /build/eclipse-che/data:/data eclipse/che:latest info --network WARN: Bound 'eclipse/che' to 'eclipse/che:7.0.0-beta-4.0' WARNING: No swap limit support INFO: Proxy: HTTP_PROXY=http://proxy.ir.intel.com:911/, HTTPS_PROXY=http://proxy.ir.intel.com:912/, NO_PROXY=intel.com,.intel.com,10.0.0.0/8,192.168.0.0/16,localhost,.local,127.0.0.0/8,134.134.0.0/16 INFO: (che cli): 7.0.0-beta-4.0 - using docker 18.09.6 / native WARN: Newer version '7.0.0-beta-4.0' available INFO: INFO: --------------------------------------- INFO: -------- CONNECTIVITY TEST -------- INFO: --------------------------------------- INFO: (che network): eclipse/che-ip:7.0.0-beta-4.0: 10.237.222.41 INFO: (che network): Browser => Workspace Agent (localhost): Connection failed INFO: (che network): Browser => Workspace Agent (10.237.222.41): Connection succeeded INFO: (che network): Server => Workspace Agent (External IP): Connection succeeded INFO: (che network): Server => Workspace Agent (Internal IP): Connection succeeded I presume I have missed forwarding a port through the ssh tunnel, and that is breaking some connectivity between the workspace and the browser? Have I missed a port forwarding, any advice on how to debug the issue? Ray K
Attachment:
signature.asc
Description: OpenPGP digital signature