Connect OBS and troubleshoot an offline engine

Understand the connection

The GA360 control application and OBS are separate components. A visible OBS process does not prove the app is connected to its WebSocket server. Use the app's engine status and connection controls to see the actual result. Managed OBS and a manually started OBS instance can use different profiles, collections, credentials or ports.

Connect deliberately

1. Open the intended app and its OBS/Engineering controls. Decide whether you are using its managed OBS setup or an existing local instance.
2. Confirm the running OBS instance, WebSocket server address and configured port. Copy the matching password where required. Do not guess that every installation uses the same port.
3. Use Connect or Start / reconnect OBS as appropriate and wait for the attempt to finish. Keep the exact error if it fails.
4. Verify the expected profile, scene collection and camera inputs. A successful connection to the wrong OBS instance is still an incorrect setup.
5. Check Program, Preview and an audio meter before completing readiness.

Common failures

A refused connection often means the controller cannot reach that address or OBS is not listening there. Authentication failure calls for checking the matching WebSocket password. A local connection and a remote engine have different transport requirements; follow the app's supported secure remote settings rather than exposing ports or weakening authentication.

Recover without losing the live output

Do not repeatedly force-stop OBS merely because the control page lost contact. Determine whether it is still streaming or recording, then reconnect to that same instance. Stop required outputs before changing profiles, collections, devices or recording configuration. Use the app's displayed blocked-output reason instead of assuming only the main stream matters.