The bridge console

The console is a web page on the machine. By default, it listens on this machine only, at 127.0.0.1. It opens on the Folders tab. A bridge that is not connected yet opens on the Connection tab.

To open it:

On Windows, click the Quix Lake Bridge icon in the taskbar and select Open console....
On any system, run quix-bridge ui to get the console address and a login code.

Open the console from another machine

To reach the console from another machine, set the console.listen key in config.yaml, then restart the service:

console:
  listen: 0.0.0.0:8330

These rules apply:

console.port sets the port. The default is 8330.
A port in console.listen wins over console.port.
console.listen takes an IPv4 address, such as 0.0.0.0 or 10.0.0.5. It does not take a host name.
The console always also listens on 127.0.0.1.
quix-bridge ui --listen <address> only picks the address that the printed URL names. It does not change where the service listens.
An address that is not loopback serves plain HTTP. Use it only on a trusted network, or behind a TLS reverse proxy.
After 5 wrong login codes, the login locks for 5 minutes.

With a loopback address, ui prints an SSH tunnel hint. Run it on your own machine, then open the URL that ui printed:

ssh -L 8330:127.0.0.1:8330 <user>@<host>

The status strip

A status strip sits above the tabs. It shows the connection state, the time the bridge connected, the number of shared folders, the number of open sockets and the version. When something is wrong, a second line names the cause, the next step and one action, such as See activity or Pair again.

An error in the status strip or on the Activity tab carries a reference. Click the copy button beside it to copy the reference, the time and the error detail. Give this text to Quix support.

The tabs

Tab	What it shows
Folders	The folder tree of the machine, with the Folder, SAG path, Status and State columns. You share folders and set the bucket root here.
Connection	The connection to Quix. You paste the quick config here.
Activity	The connection events, newest first. Each row says what happened and what to do.
Health	Two checks that change nothing. Run the folder check reads each shared folder as the service account and checks that the bridge reaches Quix. Run the reboot check looks for anything that stops the bridge after a reboot.
Config	The `config.yaml` file. A secret never appears in this file. When the file changed on disk after you opened the tab, the console refuses your save and says "config.yaml changed since you opened it. Reload the Config tab, then save again."
Log	Writes, deletes, listings and reads of files. The reads of one file by one caller join into one line. The tab shows the last 200 lines. The log holds no file content, no secret key and no token.

Install the console as an app

In Edge or Chrome, the console shows an Install bar. Click Install. Firefox cannot install the console as an app.

In Edge, tick Pin to taskbar in the install dialog.
In Chrome, right-click the app's taskbar button after install and pick Pin to taskbar.

The app opens straight into the console, with no login code, for 30 days after your last use. After 30 days, sign in again with the tray icon or a login code. When the bridge service is stopped, the app shows an offline page.

Windows 11 hides the tray icon

Windows 11 puts a newly installed tray icon behind the ^ arrow next to the clock. Click the arrow to find the Quix Lake Bridge icon. To keep it visible, go to Settings > Personalization > Taskbar > Other system tray icons and turn it on there.

Next steps

Shared folders and the bucket root — what you do on the Folders tab
Troubleshooting and limits — what the states and errors mean