The FlexViz Bridge
Bridge troubleshooting
What you see
What it usually means
- Waiting for Bridge in the browser, forever
- The Bridge is not signed in, is signed in to a different account, or the invitation expired. Invitations last about ten minutes.
- The invitation list stays empty
- Press Refresh. Check both sides use the same account.
- Bridge offline
- The pairing stands, but the Bridge is not reporting in or reports a console error. Check the Bridge window and its connection.
- Waiting for console
- The Bridge is paired and reachable, but no live DMX has arrived yet. Check the console output and source approval in the Bridge.
- Paired, but nothing moves
- The source has not been approved yet, or the desk is holding a look and sending no changes.
- The rig went dark and the Bridge still reads "approved"
- The desk's IP changed (DHCP) and came back as a new source. Answer the approval prompt for the new address, then give it a fixed address or a reservation.
- The Bridge is back at "Sign in to FlexViz" by itself
- FlexViz no longer accepts the Bridge's stored login – you signed it out elsewhere, your password or account changed, or an administrator ended it. The Bridge forgets the login and shows the sign-in again; Copy diagnostics lists FlexViz login was revoked with the time it happened. Sign in again. A Bridge that simply runs for a long time renews its login by itself and is not signed out.
- The pairing dropped when you changed scene
- Expected. A scene switch in the browser ends the pairing; invite again from the new scene.
- Art-Net nodes are not discovered
- A node whose subnet mask does not match yours needs Art-Net broadcast set to
255.255.255.255. - The Bridge or the console will not start, or one of them receives nothing
- They are on the same machine and fighting over UDP 6454 / 5568. Move the Bridge to a second machine — see the warning at the top.
Copy diagnostics, at the foot of the Bridge window, puts the current state on the clipboard for a bug report. Each error in it carries the time it happened. It may contain hostnames, IP addresses and endpoint URLs — read it before pasting it somewhere public.