Bug Report WebSocket Server Failure

[JedCrane]

When I start OBS, it crashes, saying:

WebSocket Server failure

- TCP port 4444 may currently be in use elsewhere on this system, possibly by another application. Try setting a different TCP port in the WebSocket server settings, or stop any application that could be using this port.
- An unknown network error happened on your system. Try again by changing settings, restarting OBS or restarting your system.

I didn't see a similar post on here about this, but sometimes it loads if I click OK on the WebSocket Server failure, as long as I click it BEFORE it pops up saying it crashed.

Any ideas?

Thanks :)

Here's the crash log:
https://obsproject.com/logs/oiEXiWBmSlkzZpuF

 

[_ZLD_]

Does this happen any time you start OBS or is it just during certain circumstances, such as restarting after a different crash incident?

Unless you are doing some network based programming and plugging to this socket for a project, there are only a few scenarios I can envision this error appearing as a result of the websocket plugin.

1) OBS crashed for some separate reason and you have opened OBS before the socket clears
2) your network stack is messed up and not clearing properly
3) you are using a browser that isn't properly handling websockets and continues connecting to 4444 even after OBS crashes

You seem to be getting a lot of errors in loading plugins as well. Maybe export your OBS profile and scene setup and uninstall and reinstall OBS from scratch. Possibly something has gotten screwed up with your install.

 

[kevinjustkevin]

I'm Getting the same errors since installing Touch Portal. Any way to fix this?

 

[BesTCooL]

Change in macro deck - plugins - web sockect plugins - change settings sample 4445 after change OBS web socket settings