-
-
Notifications
You must be signed in to change notification settings - Fork 699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Websocket won't start without IPv6 support #1175
Comments
I get the same error in my logs regardless of IPv6 being enabled or not on Windows 10 with OBS 30.0.0 64bit using the version of OBS Websocket shipped with OBS. Background: The next time I went to connect to obs websocket (today), it wouldn't connect again. I checked the logs and saw this:
So I went ahead and enabled IPv6 again, rebooted and I could connect ONCE (I have the System Tray alerts enabled and it showed an established connection). After restarting OBS it wouldn't let me connect again, so I unchecked
If I start OBS with
Only when I disabled IPv6 on my network interface AND threw
Funnily, I was still not able to connect again. So I replaced To complete the cycle I removed the
I do not know if a Windows update changed how |
My case might actually be explained by #1085 I will add further information there. |
The log you provided shows that the running obs-websocket version is 5.2.3, while the commit which implements the automatic ipv4 fallback was first introduced in 5.3.0: 6434c42 What method are you using to specify startup flags? I don't see how it could be still trying IPv6 unless the argument is not actually being passed to OBS. |
Operating System Info
Other
Other OS
6.5.7-arch1-1
OBS Studio Version
Other
OBS Studio Version (Other)
29.1.3 (64 bit)
obs-websocket Version
Git
OBS Studio Log URL
https://obsproject.com/logs/kg1WxufbMT6tq19g
OBS Studio Crash Log URL
No response
Expected Behavior
Related to #1131 websocket should work with the current obs version for linux.
Current Behavior
Websocket isn't starting if IPv6 isn't available for the system:
Steps to Reproduce
Anything else we should know?
When I start obs with
--websocket_ipv4_only
flag the websocket is starting. Anyway, the fix in 6434c42 won't work for the messages in my log.The text was updated successfully, but these errors were encountered: