Crosser Node 2.5.1

Crosser Node 2.5.1

Crosser Node 2.5.1

October 29, 2021

This is a minor update with some changes that didn’t make it into the main release.

Improved API documentation

The built-in swagger UI now provides more details about each endpoint.

Release-notes in UI

Since v2.5.0 the EdgeNode has a simple dashboard. This UI got minor visual updates and now also includes release-notes as of v2.5.1.

View flow logs in UI

Previously you could see the host logs in the built-in UI. Now you can also view the logs for each flow deployed on the EdgeNode.

Endpoints for killing processes disabled by default

The endpoints that can be used for terminating the host and runtimes is now by default disabled. To configure these endpoints you can edit the appsettings.json

"restApi": {
    "allowKillHostFromApi": false,
    "allowKillProcessFromApi": false, 
    "allowKillRemoteSessionProcessFromApi": false


You can also override these setting with environment variables:

EdgeNodeConfiguration__RestApi__AllowKillHostFromApi = <value>
EdgeNodeConfiguration__RestApi__AllowKillProcessFromApi = <value>
EdgeNodeConfiguration__RestApi__AllowKillRemoteSessionProcessFromApi = <value>

Disk storage changes

We previously wrote some files to the root of the application. These files do not need to be persistent. Since the interest for running the EdgeNode in Open Shift has increased we moved all temporary files into /tmp. This will make it easier to configure Open Shift and other products with similar requirements.

Module default timeout change

The default module timeout (initialize/start) was changed from 5 seconds to 30 seconds since some modules require more than 5 seconds to initialize/start. In the future this setting will be available from the UI for each module individually.

    • Related Articles

    • Crosser Node 2.5.3

      Crosser Node 2.5.3 May 2022 Bugfix - Prevent Crash When Getting ChannelClosedExceptions When running remote sessions with unstable network connections the node host process could crash due to not handling a ChannelClosed exception in a proper way.
    • Crosser Node 2.5.4

      Crosser Node 2.5.4 Note: Version 2.5.4 of the node has been pulled back due to critical issues that were identified after the release. Please upgrade to a later version. September 2022 Bugfix - Prevent Invalid Http Requests To Cause 100% CPU This bug ...
    • Monitoring the Crosser Node

      Introduction Once you have your first flows deployed, you might think about how to integrate the Crosser Node and Flows into your existing monitoring solution. In this article we describe what options you have and how to utilize provided interfaces ...
    • Crosser Node 2.5.6

      Crosser Node 2.5.6 - Performance improvements November 2022 FlowMessage Improvements In complex flows where the flow splits into several paths the FlowMessage needs to be cloned. When having large and complex structures in the FlowMessage this was a ...
    • Crosser Node 2.5.5

      Crosser Node 2.5.5 - Enhanced proxy support and critical patches September 2022 Bugfix - Enable *_PROXY Usage Previously the Crosser Node only supported HTTP_PROXY/HTTPS_PROXY, but as of v2.5.5 the list below is supported. The environment variables ...