My Node is active but I can't start a remote session
Answer
Issue: The Node shows up in the list of available Nodes when you click on "Connect to node" inside the Flow Studio, but then you never get connected (the popup stays with a spinner waiting).
When starting a remote session the Node will by default try to establish a websocket connection to Crosser Cloud. If you have some network device in between the Node and Cloud that prevents websocket sessions, such as a proxy or a firewall, you will end up with this issue. There are two ways to solve this:
- Configure your intermediate network device to allow websocket connections
- Change the Node configuration to use HTTP long-polling instead of websocket (might have an impact on interactivity but usually works fine). Follow these steps to configure your Node to use HTTP:
- Stop the Node (on the server where you installed it)
- Docker (terminal window): sudo docker-compose down
- Windows (Administrator PowerShell window): Stop-Service Crosser.EdgeNode.Service
- Windows (Services app): Right-click on the Crosser.EdgeNode.Service and select "Stop"
- Change the Node configuration file
- Open the file <node install dir>/data/endpoints.json (Docker) or <node install dir>/Host/data/endpoints.json in an editor
- Change the value of "remoteSessionTransport" from "Automatic" to "HTTP"
- Start the node
- Docker (terminal window): sudo docker-compose up -d
- Windows (Administrator PowerShell window): Start-Service Crosser.EdgeNode.Service
- Windows (Services app): Right-click on the Crosser.EdgeNode.Service and select "Start"
- Verify the configuration change in Crosser Cloud
- On theNodespage expand the row for this Node (click on the ">" symbol on the left-hand side)
- In the lower part of the expanded Node, find "endpointsConfiguration" and click on the arrow to expand. Verify that the "remoteSessionTransport" setting is now "HTTP".
- Try to setup a remote session in the Flow Studio