Connect XPression on the Same or a Remote Computer

Configure host addressing, DataLinq, ports, firewalls, and connection tests for local or LAN workflows.

Written By 4ALL.LIVE

Last updated About 1 month ago

Configure host addressing, DataLinq, ports, firewalls, and connection tests for local or LAN workflows.

Best for: XPression operators, graphics engineers, caption operators, broadcast engineers, production IT, and licensed desktop administrators.

Before you start

Requires an active 4All organization/event, authorized desktop account, eligible XPression Bridge license, supported app build, and a network path to 4All plus the selected XPression protocol.

  • Document the 4All event/language and XPression scene/DataLinq design.
  • Know the bridge/XPression machines, IP interfaces, protocol, direction, port, firewall owner, and final program return.
  • Prepare a backup output and an off-air test scene.

Step by step

  1. Decide topology. Bridge on XPression machine or separate LAN machine.
  2. Same computer. Use the app’s same-computer host/URL guidance and avoid local port conflicts.
  3. Remote computer. Use the listed reachable LAN interface/address, not localhost.
  4. Choose one protocol/port. Document server/client direction.
  5. Create firewall rule. Allow only the selected app/protocol/port/profile/source network.
  6. Configure XPression DataLinq/ingest. Use generated URL/host/port and payload mapping.
  7. Test connectivity. Confirm XPression connection count/status.
  8. Test fields. Caption, line1/line2/line3, speaker/language as mapped.
  9. Reboot/reconnect test. Confirm XPression and Bridge start order.
  10. Lock configuration. Static address or reliable DNS where needed.

What success looks like: The Bridge transports the correct 4All caption state to the intended XPression scene with verified formatting, timing, monitoring, and recovery.

Check your setup

  • XPression connects from the intended machine, receives test/live captions, and recovers after either side restarts.

Troubleshooting

localhost used remotely

Replace with Bridge LAN address.

Firewall blocks

Create scoped inbound/outbound rule for connection direction.

Multiple adapters

Choose the interface reachable from XPression and avoid VPN ambiguity.

Security and operational notes

  • Do not bind to all interfaces unless required and approved.
  • Use trusted production LAN.
  • Coordinate restart/on-air scene ownership.

Documentation status: Draft based on XPression Bridge repository version 0.1.59. Validate the installed release, supported OS, license policy, and live graphics workflow before publishing.