Cloudless Fluid#

Cloudless Fluid is a connection method for reaching a host over Fluid by hostname or IP address, with no Jump cloud service in the connection path. Because connections do not pass through the Jump cloud, Cloudless Fluid works for hosts without internet access. Use it on isolated or high-security networks, for example for hosts reachable only over your VPN. To compare other options, see Choose a connectivity option.

Applies to#

• Jump Desktop for Teams Enterprise plan.
• Team administrators turn on Cloudless Fluid; end users connect.
• Hosts running Jump Desktop Connect on Windows, macOS, or Linux Alpha.
• Jump Desktop on Windows, macOS, iPhone, or iPad, signed in to an account on the Jump Desktop for Teams Enterprise plan. Otherwise, the app refuses Cloudless Fluid connections, including connections from launch URLs.
• Jump Desktop for Android and the web browser client cannot make Cloudless Fluid connections.

Before you start#

Allow the following traffic from clients to the host:

Turn on Cloudless Fluid#

Turn on Cloudless Fluid for each host by using either of the following methods.

From the Teams dashboard: in a Connect Configuration, select Manual Fluid Connections. Optionally, change Manual Fluid Port. Assign the configuration to the hosts.

On the host (Windows or macOS, for example when the host has no internet access):

1. Open Jump Desktop Connect and go to Settings > Advanced.
2. Verify that Fluid Remote Desktop is turned on.

3. Select Manual Connections (requires Teams subscription). Optionally, change Port.

   

The option is unavailable (greyed out) unless Fluid Remote Desktop is on and local changes are allowed. On a host with a Connect Configuration, local changes require the Local Configuration Changes setting in that configuration.

From the command line (Connect 10.12.15 or later): run Connect with --serverconfig RtcLocalServer=true, and also with --serverconfig RTCEnabled=true if Fluid Remote Desktop was turned off. See Enable Cloudless Fluid and get its launch URL from the command line.

Connect#

Launch URL: on the host, in Settings > Advanced, click Copy Launch URL. If users reach the host by a different name or IP address, edit the host name in the URL. Send the URL to users. To print the URL from the command line instead, run Connect with --cloudlessurl (see Enable Cloudless Fluid and get its launch URL from the command line). The URL pins the host's fingerprint, so Jump Desktop refuses a host with a mismatched fingerprint. See Launch links and connection files.

Add manually (Windows and macOS):

1. In Jump Desktop, click File > Add New....
2. For Type, choose Fluid.
3. Enter the Host as a hostname or IP address. Append :port if the host does not use port 35384.
4. Enter a Name and add the host.

Add manually (iPhone and iPad): in the computer list, tap +, set Type to Fluid, and enter the Host and Port (default 35384).

Verify the fingerprint#

The first time you connect to a manually added host, Jump Desktop displays Verify Fingerprint. Compare the displayed fingerprint with View Fingerprint under Settings > Advanced in Connect on the host. Click Trust and Continue only if the fingerprints match.

If the fingerprint changes later, click Reject (Recommended) unless you expected the change.

Then sign in with a local user account on the host.

Connect through a gateway#

A gateway that forwards traffic to hosts on a private network, such as the gateway of a connection broker, can carry Cloudless Fluid connections when clients cannot reach the host's own addresses. Add the gatewayudp parameter to the launch URL so that Jump Desktop also sends Fluid's UDP session traffic to the gateway.

Requires Jump Desktop 10.12.15 or later on Windows, macOS, iPhone, or iPad. Using a host name in gatewayudp requires Jump Desktop 10.13.2 or later. The host needs no change.

Configure the gateway with two forwards to the host:

For example:

jump://203.0.113.10:34000?protocol=fluid&SSLFingerprint=<fingerprint>&rtcv2=true&OSTypeCode=1&gatewayudp=203.0.113.10:34001

Start from the host's launch URL (see Connect), replace its host name and port with the gateway's TCP endpoint, and append gatewayudp.

• gatewayudp takes one endpoint: an IPv4 address, an IPv6 address in brackets ([2001:db8::10]:34001), or a host name, followed by : and a port from 1 to 65535. The port is required.
• Jump Desktop resolves a host name when the connection starts, and offers the gateway endpoint alongside the host's own addresses; the connection uses whichever path works.
• Jump Desktop ignores a gatewayudp value it cannot parse, or a host name it cannot resolve, and connects without the gateway endpoint.
• gatewayudp applies only to Cloudless Fluid connections. Connections through the Jump cloud ignore it, and Jump CLI accepts the parameter but does not use it.

Restrict access by user or group#

Because team access controls do not apply, any user with a local account on the host can sign in. On Windows, the account must also be a member of the Administrators or Users group and, with Connect 10.15.28 or later, must hold the Allow log on locally right. To allow only specific users or groups, turn on Local Authentication Restrictions in the Connect Configuration assigned to the host. The restrictions apply to both Cloudless Fluid sign-ins and connections through the Jump cloud.

Related#

• Choose a connectivity option
• Network requirements
• Configure computers with Connect Configurations
• Launch links and connection files
• Enable Cloudless Fluid and get its launch URL from the command line