Network Troubleshooting

Available

Most CueForge integration issues are network issues. This guide covers systematic diagnosis and resolution.

Before you start

1. Confirm both devices are on the same network or have a valid route.
2. Verify cables, switches, and Wi-Fi connections.
3. Check that no firewall is blocking the required port.

Quick diagnosis checklist

1. Ping test

From the CueForge machine, ping the target device:

ping <target-ip>

If ping fails, the devices cannot communicate at the IP level. Check:

• IP addresses
• Subnet masks
• Physical connections
• Firewall rules

2. Port test

Use telnet or nc to test the specific port:

telnet <target-ip> <port>
# or
nc -vz <target-ip> <port>

If the port test fails, check:

• The target service is running
• The target is listening on the expected port
• No firewall blocks that port

3. OSC-specific test

Use a tool like Protokol or OSCulator on the target machine to verify OSC messages are arriving.

4. MIDI-specific test

Use a MIDI monitor tool to verify MIDI messages are arriving on the correct channel.

Common problems

”Connection refused”

• The target device is not listening on that port.
• The target service is not running.
• Wrong IP address.

”No route to host”

• Devices are on different subnets without a route.
• Wrong subnet mask.
• Physical disconnection.

”Request timed out”

• Firewall blocking ICMP (ping).
• Target device is powered off or asleep.
• Network congestion or faulty cable.

OSC messages not received

• Wrong port on target.
• Target bound to a specific interface (e.g., localhost only).
• Wrong OSC address pattern.

MIDI device not visible

• Device not connected or not powered.
• Driver issue on the OS.
• Device in use by another application.

Best practices

• Use static IPs or reserved DHCP leases for production networks.
• Document the IP and port of every device in your show.
• Label cables and ports clearly.
• Test the network before every show, especially in new venues.

Current limitations

• CueForge does not include built-in network diagnostics. Use OS-level tools.