Connection Modes

ℹ️ About This Page

INFRAX uses two connection types for remote nodes: the browser client and the native client. Browser sessions open in the embedded window by default, can be minimized and switched, and can be moved to a separate browser tab when needed.

Section Contents

Mode Overview

The connection picker shows two cards: Browser client and Native client. The choice is remembered in the browser, and INFRAX automatically limits the available mode for some protocols.

Protocol Support

Protocol Browser Client Native Client Notes
RDP Yes Yes The user can choose the mode manually or reuse the saved preference
SSH Yes Yes Both browser-based and native launches are available
VNC Yes No Always opens in the browser client
Console Yes No Always opens in the browser client
Winbox No Yes Native launch is available only on Windows and macOS
Web Yes No Opens the saved URL in the browser
⚠️ Important Limits

Console and VNC always run in the browser client. Winbox only works through the native client, and session recording is available only for browser-based connections.

Browser Client

In the picker this mode is labeled Browser client. It runs in the browser through Apache Guacamole and opens sessions in the INFRAX overlay by default.

What Happens on Connect

  • The session opens inside the INFRAX interface
  • The active connection can be minimized while you work elsewhere
  • If several sessions are minimized, you can switch between them from the header panel
  • Browser connections can be moved to a separate browser tab
  • Recording is available for browser connections, but not for native ones
  • RDP, SSH, VNC, Console, and direct Web URLs are supported

Connection Controls

  • Node title - shows the node name and protocol tag
  • Switch connection - opens the list of minimized sessions
  • Open in a new tab - moves the session to a separate browser tab
  • Minimize (Esc) - hides the session into the top bar
  • Close - ends the connection
ℹ️ Additional Note

Browser connections use the built-in toolbar, and the opening mode can be changed in User Settings → Interface → Remote connection opening mode.

Native Client

The native mode launches local client applications through the Infrax plugin and the xrdp://, xssh://, and xwinbox:// URL schemes.

What It Supports

  • RDP - opens the local RDP client
  • SSH - opens the local SSH client
  • Winbox - launches Winbox for MikroTik devices
  • Use all monitors - an extra option for RDP

Requirements

  1. Install the Infrax plugin
  2. Have the local client applications installed
  3. Use Windows or macOS for Winbox
⚠️ Limitations

If the application setting for web-only connections is enabled, the native mode is not available. The app shows an error if someone tries to launch a native connection anyway.

Choosing a Connection Mode

When a connection starts, INFRAX shows the Choose connection method dialog. It contains the Browser client and Native client cards, plus the save-selection option.

Dialog Elements

  • Use all monitors - shown only for native RDP
  • Remember this choice for future connections - stores the connection type in the browser
  • Download Infrax plugin - shown when the native client is required
  • Type hint - explains the selected mode limitations
ℹ️ Default Behavior

VNC and Console do not show the dialog at all, because they always open in the browser client. Winbox is the opposite: only the native client is available.

The saved selection is stored in the browser as preferred_connection_type.

Browser Opening Mode

The Remote connection opening mode setting controls where browser sessions appear after launch.

  • Open inside the embedded window (iframe) - the default mode. Connections stay inside INFRAX.
  • Open in a new browser tab - the session opens in a separate tab immediately.
✅ When to Use It

The embedded mode is convenient for everyday work and switching between several sessions. A new tab is useful when you want to move a connection to another monitor or keep it separate.

Admin Settings

An administrator can disable native connections with the Allow connections only through the web client option in Connections and session recordings.

What Changes When It Is Enabled

  • The native card in the picker becomes unavailable
  • RDP and SSH connections continue to work through the browser client
  • A native launch attempt ends with an error message
  • Session recording stays available only for browser connections
⚠️ Typical Use Case

This setting is useful when you need centralized activity recording, want to restrict local clients, or want one access method for the entire team.

Best Practices

When to Choose the Browser Client

  • You need session recording
  • You are working from shared or untrusted computers
  • You cannot install the Infrax plugin
  • You need to open a connection quickly without local apps
  • You want to switch between multiple sessions in one window

When to Choose the Native Client

  • You need maximum performance
  • You need full protocol functionality
  • You want all monitors for RDP
  • You work with MikroTik devices through Winbox
  • You run long and frequent sessions
💡 Practical Tip

For day-to-day work, it is convenient to keep the embedded window as the default and move a session to a new tab only when needed. If you need full control or recording, use the browser client. If you need maximum speed and Winbox, use the native client.