![]() |
DLNA Errors, Jellyfin uses old IP - Log is exploding - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: DLNA Errors, Jellyfin uses old IP - Log is exploding (/t-dlna-errors-jellyfin-uses-old-ip-log-is-exploding) |
DLNA Errors, Jellyfin uses old IP - Log is exploding - Tone - 2025-10-23 I noticed my logs are getting huge (~90MB per day), so my fail2ban isn't working anymore because of the size. I noticed the problem comes from the DLNA plugin: Code: at Rssdp.Infrastructure.SsdpCommunicationsServer.SendFromSocket(Socket socket, Byte[] messageData, IPEndPoint destination, CancellationToken cancellationToken) │ I've installed jellyfin with docker (official repo) and used it first in normal nat-mode. However, I got problems with my reverse proxy in combination with the webos client, so I had to directly connect my tv with jellyfin. So I set network_mode to host. This was many months (if not years) ago. But if I read the log correctly the dlna-plugin still uses the docker-nat-ip 172.16.17.1, which I guess is causing the problem. I havn't found this IP anywhere in the configuration, so I don't know, why it uses this IP anymore. Anyone has a idea how I can fix it? RE: DLNA Errors, Jellyfin uses old IP - Log is exploding - Tone - 2025-10-23 Ok, I checked with tcpdump. Looks like it uses the normal host ip. Don‘t know where the log gets the old ip. But then the question is what else is the issue. |