How to Resolve Jellyfin Port Conflict Issues on zimaos v1.2.5

We apologize for the inconvenience.

In ZimaOS version 1.2.5, Windows LAN device discovery and DLNA services have been added, which may occupy port 1900 of Jellyfin. You can follow the steps below to disable the related services:

systemctl stop minidlnad.service
systemctl disable minidlnad.service
systemctl stop ssdpd.service
systemctl disable ssdpd.service

Once this is done, restart Jellyfin to solve the problem.

We’ll disable these services by default in the next release, sorry again!

1 Like

the problem was solved after following your instructions, but after rebooting, the problem reappeared.

Error response from daemon: Cannot restart container bf5e43043f896cb311a9396d9feebc3cdfd4e638fcbe2bfe2b20994dcf1d5f88: driver failed programming external connectivity on endpoint jellyfin (25f2fd7ecf13ca08f372f794907847d93efca0ae53f4bbe749e0a845c677be9f): failed to bind port 0.0.0.0:1901/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:1901: bind: address already in use

The reason for this issue is our new service for UPNP device broadcasting, which occupies port 1901, which is mainly used for the discovery of Windows network devices. The reason for the failure after the reboot should be that the SSDPD service is not really disabled.
Anyway, we are aware of this problem and have moved the 1901 port of the ssdpd to a different port, this issue will be fixed in the next release, until then you may still need to manually execute systemctl stop ssdpd.service after boot I hope you understand.

1 Like

after ZimaOs reboot minidlnad service start again