Skip to content
CornetaPortuguês

Help center · Troubleshooting

Corneta can't find OBS: WebSocket, password, port, firewall

In OBS, open Tools → WebSocket Server Settings, keep the server enabled and copy the same password into Corneta. Corneta always looks for OBS on port 4455; if you changed the port in OBS, set it back to 4455.

Published
Reading time
2 min read
Corneta version
0.11.0
Tested with
Corneta 0.6.0 (Windows 11), OBS Studio 32.x (Windows 11)

First test

In OBS 28 or later, open Tools → WebSocket Server Settings. WebSocket comes built in; don't install a separate plugin unless you need to.

  1. Turn on the WebSocket server.
  2. Check that Server Port is set to 4455. Corneta doesn't let you change this port.
  3. Keep Enable Authentication on.
  4. Click Show Connect Info, copy the password and paste it into Settings → OBS in Corneta.
  5. Click Test connection or go back to Hook up OBS.

Enlarge image

Fit
Corneta screen with the OBS connection set up and the local input details.

The WebSocket controls OBS; the local RTMP address receives the video. They are two different paths.

The WebSocket controls OBS; the local RTMP address receives the video. They are two different paths.Source: CornetaCorneta version: 0.11.0

By symptom

Message in CornetaLikely causeFix
Couldn't find OBSOBS is closed, the WebSocket is off or the port isn't 4455. Up to 0.8.5, a wrong password also shows up this wayopen OBS, turn on the server, set the port back to 4455 and copy the password again
Password refusedOBS asks for a password and Corneta has none or, after 0.8.5, a different onepaste the password into Settings → OBS
Connected, but OBS isn't pointing at CornetaOBS is streaming to another serverclick Set it up for me on the Live screen
Connected, but Waiting for signalthe WebSocket is fine; the video hasn't arrivedstart streaming in OBS

If OBS froze, close it and open it again. Antivirus software with its own firewall can also block the connection: allow OBS and Corneta in it.

Don't turn off the password just to “see if it works” on a shared network. The OBS documentation recommends protecting the WebSocket.

If it keeps happening, write down the message and the versions. Never send the WebSocket password.