Connecting to Titan
All Livelabs Creative apps connect to your Titan console via the Titan WebAPI.
Every app has a connection field at the top of the interface where you enter your console's IP address. The connection status is shown in the status bar — once connected, you're ready to use the app. There are two ways to connect: auto console detection, which automatically finds your console or Titan session on the network, or manually, by entering the console's IP address directly.
To switch between modes, use the Auto Detect toggle to the left of the IP field — enable it to use auto detection, or turn it off to enter manual mode. In manual mode, the combo box becomes a text entry field where you can type the console's IP address directly.
Use 127.0.0.1 as the IP address instead. This is faster than connecting over a network.
Automatically connecting to Titan
When auto detect is enabled and the detect button is pressed, the app scans all available networks for Titan sessions. Note that Livelabs Creative apps do not generally connect to a Titan Net session.
If you are running a Livelabs Creative app on the same machine as Titan, the optimal approach is to switch to manual mode and enter the loopback address (127.0.0.1) directly — auto detection will find a network adapter rather than the loopback, which is slower. In some cases, auto detection may connect to 127.0.0.1 automatically, but this is not guaranteed.
Manually connecting to Titan
Finding your console IP
- Press Avo + Disk to open the System menu
- Press Softkey A — Network Settings
- Your IP address for each network interface is listed in this menu
Connecting in the app
- Launch the app
- Enter the console IP address in the connection field
- Click Connect
A green status indicator means you're connected and ready to go. Once connected, the Connect button changes to Refresh — clicking it pulls the latest data from the console.
On the first connection attempt of a session, the app may report a connection failure. Press Connect again and it should go through.
Troubleshooting connection issues
Same network
Both your PC and the Titan console must be on the same network and subnet. A common setup is both devices connected to the same router or switch via ethernet or Wi-Fi.
If your PC has multiple network adapters (e.g. ethernet and Wi-Fi both active), make sure the one used to reach the console has an IP address in the same range as the console. For example:
| Device | IP Address |
|---|---|
| Console | 192.168.1.10 |
| Your PC | 192.168.1.25 |
Both start with 192.168.1. — they're on the same subnet. If your PC shows 192.168.2.x on one adapter, that adapter is on a different subnet and won't reach the console.
Test with ping
Open a Command Prompt or Terminal and run:
ping <console-ip>
If you get replies, the network path is good and the issue is likely firewall-related. If the ping times out, the devices can't see each other — check cables, switches, and network adapter settings.
Firewall
A firewall on your PC can silently block the connection even if the network is fine. Temporarily disable it to test — if that fixes it, add an exception for port 4430 rather than leaving the firewall off.
Titan Simulator — firewall rules
If the app repeatedly fails to connect and you are running Titan Simulator, Windows firewall may be blocking the WebAPI port. You can add the required rules via Command Prompt or PowerShell.
The following commands open port 4430 on your Windows firewall. Only do this on a trusted local network.
Run the following commands as Administrator:
netsh advfirewall firewall add rule name="Avolites WebAPI Inbound" dir=in action=allow protocol=TCP localport=4430
netsh advfirewall firewall add rule name="Avolites WebAPI Outbound" dir=out action=allow protocol=TCP localport=4430
Once run, try connecting again.