[BUG] OBS crash on startup with sender enabled

[stashymane]

Beam crashes host OBS on startup if the sender is enabled.
I used to have this issue only when the receiver is already running, but now I receive it regardless.

22:02:23.935: [xObsBeam] Peer Discovery server: Starting for Output "Beam Sender Output" on ****:****...
22:02:23.935: [xObsBeam] Listening on ****:****.
22:02:23.935: [xObsBeam] Failed to start TCP listener for Beam Sender Output on ****:****, try configuring a different port or use a different interface.
22:02:23.939: [xObsBeam] InvalidOperationException in BeamSender.Start: Not listening. You must call the Start() method before calling this method.
22:02:23.939:    at System.Net.Sockets.TcpListener.AcceptSocketAsync(CancellationToken) + 0x12f
22:02:23.939:    at xObsBeam.BeamSender.<Start>d__38.MoveNext() + 0x77b

The configured port is not used by anything else according to TCPView.
My config: xObsBeam.json
Full log: 2024-04-19 22-07-13.txt

[YorVeX]

Will try to reproduce it by intentionally blocking a port, the one part that shouldn't happen is that this crashes OBS (an error message and Beam then not working can't be avoided in such cases though).

As for why it happens for you without the port being used I don't know, most likely scenario would be a firewall blocking it. Can you please try to reboot your computers, then before doing anything else temporarily disable all security suites and firewall software, then start OBS and see whether you still get the message?
I mention security suites because I've seen cases where even a generic anti-virus software surprisingly had firewall functionality included without making that clear to the user, causing lots of headaches before finding out about it. And of course the Windows firewall should also be disabled for the test.