The Node communicates with the Crosser Control Center is using HTTPS on port 443. The HTTPS port is also used by many modules that connects to web services. All traffic is initiated from the Node, so this port must be open for outbound traffic. Locally port 9090 is used for inbound HTTP(S) traffic to the HTTP Listener module and port 1883 / 8883 for inbound MQTT traffic (MQTT Sub Broker/Client modules). The local web UI and API is accessed through port 9191. Inbound port mappings are configurable.

Yes, the Crosser Node needs to be configured locally when sitting behind a proxy. See here for more information. By default Crosser Nodes use websocket communication with Crosser Control Center during remote sessions, so if the proxy does not support websockets the default configuration needs to be changed.

The Crosser Node runs as a Linux container, which is currently not supported by the enterprise version of Docker on Windows. 

The code modules available in the Crosser Module library are very powerful when you need to run your own custom logic or need additional functionality.

Use Template Modules for data mapping when you need to create a complex message structure with lots of static data/hierarchies.

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). Learn the two ways to solve this issue.

Crosser Cloud is hosted in Azure West-Europe region (Amsterdam).

Very useful module to limit the rate of messages for enhanced overview and debugging.

Use the Timeout module to monitor the expected delivery of data and get notified when data stops arriving.

Yes, use CTRL+C and CTRL+V in the FlowStudio to achieve this.