Hi, what could be preventing me from connecting to the WebSocket of a local instance of OBS on LAN between two Windows 10 machines?
My logfile: https://obsproject.com/logs/qOvxqhZZtYW0iOjv
Logfile analysis: https://obsproject.com/tools/analyzer?log_url=https://obsproject.com/logs/qOvxqhZZtYW0iOjv
21:33:17.171 = attempt to connect with http://propz.de/obs-websocket-tester (i.e, there was no WebSocket Debug log output)
21:33:35.773 = attempt to connect with http://obs-web.niek.tv
- WebSocket works fine on localhost / when accessed in a browser running on the machine running OBS (tested with http://obs-web.niek.tv)
- On any other system, it doesn't connect - http://propz.de/obs-websocket-tester says "Error connecting to OBS: Security the operation is insecure" (I have authentication enabled in WebSocket settings, and it's working fine with OBS Notifier) and http://obs-web.niek.tv produces the "Authentication failed" debug log output.
- For all the above pages, I loaded them in HTTP mode via exceptions to HTTPS mode in Firefox, to be sure
- I enabled debug logging in the websocket settings in OBS, and watched the logfile with auto refresh in Notepad++. Each time I tried to connect, there was no new entry added to the log.
- I've upgraded to the latest OBS version (32.0.2) and already ran Check File Integrity which is safe.
- In Windows Firewall, I've added inbound and outbound "allow" rules for all exe files in the OBS directory recursively on the machine running OBS. I used "Firewall App Blocker" to do this, and verified the rules were applied via windows built in UI. Rebooted for good measure. Apparently none of that is even necessary tho...
- My router is an ASUS router on the latest firmware and I don't have issues with any other LAN based software.
Overall it seems something somewhere is blocking the WebSocket authentication, and I have no logs to post, because it's seemingly not even an OBS issue? But I'm only experiencing an issue like this with OBS.
My logfile: https://obsproject.com/logs/qOvxqhZZtYW0iOjv
Logfile analysis: https://obsproject.com/tools/analyzer?log_url=https://obsproject.com/logs/qOvxqhZZtYW0iOjv
21:33:17.171 = attempt to connect with http://propz.de/obs-websocket-tester (i.e, there was no WebSocket Debug log output)
21:33:35.773 = attempt to connect with http://obs-web.niek.tv
- WebSocket works fine on localhost / when accessed in a browser running on the machine running OBS (tested with http://obs-web.niek.tv)
- On any other system, it doesn't connect - http://propz.de/obs-websocket-tester says "Error connecting to OBS: Security the operation is insecure" (I have authentication enabled in WebSocket settings, and it's working fine with OBS Notifier) and http://obs-web.niek.tv produces the "Authentication failed" debug log output.
- For all the above pages, I loaded them in HTTP mode via exceptions to HTTPS mode in Firefox, to be sure
- I enabled debug logging in the websocket settings in OBS, and watched the logfile with auto refresh in Notepad++. Each time I tried to connect, there was no new entry added to the log.
- I've upgraded to the latest OBS version (32.0.2) and already ran Check File Integrity which is safe.
- In Windows Firewall, I've added inbound and outbound "allow" rules for all exe files in the OBS directory recursively on the machine running OBS. I used "Firewall App Blocker" to do this, and verified the rules were applied via windows built in UI. Rebooted for good measure. Apparently none of that is even necessary tho...
- My router is an ASUS router on the latest firmware and I don't have issues with any other LAN based software.
Overall it seems something somewhere is blocking the WebSocket authentication, and I have no logs to post, because it's seemingly not even an OBS issue? But I'm only experiencing an issue like this with OBS.
Last edited: