couldn't bind socket afte api on/of/on

[Rob Govers]

Hello,
I have a problem with the remote api.
First i set the remote api on, no problem.
Then i set the remote api off, no problem.
But when i set the remote api on again then i get the message: couldn't bind socket
Only after a ful reset of radioboss it works again, but only on and off, after that the error comes again.....
i use Radioboss 7.1.5.1

Regard Rob

 

[djsoft]

But when i set the remote api on again then i get the message: couldn't bind socket

I did a quick test and this doesn't happen here. So probably it's specific to your system (maybe, antivirus interferes).

 

[Rob Govers]

I did a quick test and this doesn't happen here. So probably it's specific to your system (maybe, antivirus interferes).

It works fine, but not when a stream / encoder is active. The firewall on or off makes no difference.
When no stream encoder is active it works fine.

 

[rajatmeti]

The error usually happens because the socket isn’t being released properly when the Remote API is turned off and then back on again. That means the port is still “in use,” so when you try to enable it again, RadioBOSS can’t bind to it.

1. Check port conflicts – Make sure no other application or background process is using the same port as the Remote API.
2. Wait a few seconds before re-enabling – Sometimes the OS needs a short time to fully release the socket.
3. Change the port – In the Remote API settings, try assigning a different port number and see if it works without restarting.
4. Run as Administrator – If you’re on Windows, try starting RadioBOSS with elevated privileges to ensure proper socket binding.
5. Contact support/update – If the issue persists, it could be a bug specific to version 7.1.5.1. Consider updating to the latest build or contacting RadioBOSS support with the details.

This way you can narrow down whether it’s a system-level port release issue or something in RadioBOSS itself.

 

[djsoft]

It works fine, but not when a stream / encoder is active. The firewall on or off makes no difference.
When no stream encoder is active it works fine.

Streaming and remote API are unrelated and do not affect each other. One thing is that you can configure internal streaming server to operate on the same port as remote API (default is 9000), in this case one of them will occupy the port and the other will show an error.

The error usually happens because the socket isn’t being released properly when the Remote API is turned off and then back on again

Please do not post "AI" content here. We believe in real conversation.