-
Notifications
You must be signed in to change notification settings - Fork 162
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
version 4.x : "The SSDP listener could not bind to the port 1900/UDP" #62
Comments
You may be running another DLNA server using this port (e.g. miniDLNA). This port is used for client discovery in pulseaudio-dlna 4.x and it can't be accessed if another server used it. You may have to stop the other DLNA server before using pulseaudio-dlna. |
Takkat is right. I am planning to make a small adjustment in the next version, where a used port or perhaps a flag just disables the auto discover feature, so that pulseudio-dlna and other DMS can live in co-existance and harmony. |
Thank you for your answers. The options "multicast/RTP receiver" and "multicast/RTP sender" and some others linked to network were enabled in pulseaudio. After disabling it, I was able to use the last version perfectly. I conjecture that it is linked to the port you mentioned. Thanks again for your work. |
|
Thanks for "pulseaudio-dlna", it is generally very usefull.
I was using "pulseaudio-dlna" on a Linux Mint 17.2 Cinnamon 64-bit computer to push the sound on my HiFi music player Sony:CMT-SBT300W. It worked fine with the 3.5 version.
After an update to 4.3 version, "pulseaudio-dlna" terminates with this message (whether the musicplayer is connected or not) :
"pulseaudio dlna.application ERROR The SSDP listener could not bind to the port 1900/UDP. Perhaps this is already in use? Application terminates"
I am back to 3.5 and it works again.
The text was updated successfully, but these errors were encountered: