OBS Remote Control

OBS Remote Control connection troubleshooting

If OBS Remote Control cannot connect to OBS Studio, work through these checks in order. Most problems come from the WebSocket settings or the network between the two devices.

Quick checklist

  1. OBS Studio is running and the WebSocket server is enabled.
  2. The controller uses the computer's local IP address, not localhost.
  3. The port and password match the OBS WebSocket settings.
  4. Both devices are on the same network.

New to the app? Start with the setup guide for controlling OBS from your phone or browser.

The WebSocket server is not enabled

In OBS Studio open Tools → WebSocket Server Settings and make sure Enable WebSocket server is ticked and applied. Keep OBS running while you connect.

The IP address or port is wrong

Use the local network IP address of the computer running OBS (for example 192.168.x.x), and the Server Port shown in the same settings window. OBS uses 4455 by default. The address can change when the computer reconnects to the network, so recheck it if a previously working connection fails.

The password is incorrect

If authentication is enabled, enter the server password exactly as shown in the WebSocket Server Settings. Copy it from OBS rather than retyping it, and watch for extra spaces. If you are unsure, generate a new password in OBS, apply it, and update the app.

You used localhost or 127.0.0.1

localhost and 127.0.0.1 always refer to the device you are typing on. From a phone or tablet they point at that device, not your OBS computer. Use the computer's local network IP address instead.

The devices are on different or isolated networks

The controller and the OBS computer must be able to reach each other. Check that both are on the same router or Wi-Fi network. Guest networks, some public or work networks, and routers with “client isolation” enabled can block devices from reaching one another, and a computer on Ethernet and a phone on a separate guest Wi-Fi may not be able to connect.

A firewall is blocking the connection

A firewall or security tool on the OBS computer may block incoming connections to the WebSocket port. Check that it allows OBS Studio on your private network, or allows the port shown in the WebSocket settings, for that network only. Avoid disabling the firewall entirely.

The browser controller will not connect but the Android app does

Web pages follow browser security rules that native apps do not, so the browser controller can be more restricted than the Android app. Try the Android app to check whether your OBS settings and network are working. If only the browser fails, test another browser or device. A common cause is that the HTTPS-hosted browser controller cannot open an unencrypted connection to a local IP address; see using the browser controller over HTTPS, which covers SSL tunneling and entering an https:// address in Server Host. If you use a tunnel that exposes OBS to the internet, keep strong authentication enabled. This site cannot confirm the exact cause in every case.

Still stuck?

Review the setup guide from the start, or see the frequently asked questions.