9 hours ago
Thank you for providing the detailed log file. I've analyzed it, and it reveals a few key things that are likely causing the connection issues with your DLNA device and iPhone app.
Let's break down the problem and the solution.
Analysis of Your Jellyfin Log
The log file is very helpful. Here are the most important findings:
The DLNA "Connection refused" Error:
This is the most prominent error in your log:
[ERR] Jellyfin.Plugin.Dlna.Main.DlnaHost: Error updating device info for "BDP-S6700"
System.Net.Http.HttpRequestException: Connection refused (192.168.1.55:52323)
---> System.Net.Sockets.SocketException (111): Connection refused
This error means that your Jellyfin server (192.168.1.253) tried to connect to your Blu-ray player (192.168.1.55) on port 52323, but the Blu-ray player actively refused the connection. This is part of the DLNA protocol where the server tries to get more information from the client. While this error is present, it might be a symptom of a larger networking issue rather than the root cause.
The Network Binding Instability:
This is the most critical issue. I can see in your logs that the Jellyfin server was restarted multiple times, and its network binding changed.
Good Configuration (at 18:10 and earlier):
[INF] Jellyfin.Networking.Manager.NetworkManager: Bind Addresses ["192.168.1.253"]
[INF] Jellyfin.Plugin.Dlna.Main.DlnaHost: Registering publisher for "urn:schemas-upnp-org:device:MediaServer:1" on "192.168.1.253"
Here, Jellyfin correctly binds to your NAS's specific IP address and advertises its DLNA service on that address. This is what you want.
Bad Configuration (at 18:19 and 18:27):
[INF] Jellyfin.Networking.Manager.NetworkManager: Bind Addresses ["0.0.0.0"]
[INF] Jellyfin.Plugin.Dlna.Main.DlnaHost: Registering publisher for "urn:schemas-upnp-org:device:MediaServer:1" on "127.0.0.1"
This is a major problem. 127.0.0.1 is the "localhost" address, meaning the server is advertising itself only to itself. Your Blu-ray player and iPhone will never see the DLNA server if it's advertised on this address.
Why Linux Works but iPhone/DLNA Fails:
You can connect from your Linux machine because you are likely using a web browser and navigating directly to http://192.168.1.253:8096. This is a direct connection and doesn't rely on network discovery.
DLNA clients (like your Blu-ray player) and the Jellyfin mobile apps rely on a discovery protocol called SSDP, which uses UDP broadcasts on the network. If the server is misconfigured to advertise itself on the wrong IP, discovery fails, and the clients won't find the server.
The constant restarts and changing network bindings suggest there might be an issue with how the networking is configured either in the Jellyfin dashboard or in the container's environment/YAML file, which might have been affected by the 10.10.7 update.
How to Fix It: A Step-by-Step Guide
Let's walk through the steps to stabilize your network configuration and get your devices connected again.
Step 1: Check Jellyfin Network Settings
The easiest place to start is inside the Jellyfin web interface.
Access your Jellyfin server from your Linux machine's web browser (http://192.168.1.253:8096).
Navigate to Dashboard > Networking.
Check the following settings:
Bind to local network address: This is the most important setting. Do not leave it blank. Select your NAS's IP address (192.168.1.253) from the dropdown menu. This will force Jellyfin to use the correct network interface.
Local HTTP port number: Ensure this is set to 8096.
Published Server URL: Ensure this is set to http://192.168.1.253:8096
Scroll down and click Save.
Restart the Jellyfin container from the Synology Container Manager.
Step 2: Check Jellyfin DLNA Settings
In the Jellyfin Dashboard, go to Dashboard > DLNA.
Ensure that Enable DLNA is checked.
You can leave the other settings at their defaults for now.
Click Save.
Step 3: Verify Container Network Mode (Crucial for DLNA)
DLNA's discovery protocol (SSDP) can be tricky with Docker's default bridge network mode.
Recommended: host network mode. For services like Jellyfin that rely on network discovery, using the host network is much more reliable. It makes the container share the network stack of your Synology NAS, eliminating any issues with port mapping or broadcast traffic.
Alternative: bridge network mode. If you must use bridge mode, you need to ensure you have correctly mapped the necessary ports in your YAML file or Container Manager settings:
8096:8096/tcp (for the web interface)
1900:1900/udp (for DLNA/SSDP discovery)
You may also need to map port 7359/udp for client discovery.
I strongly recommend switching to host networking if you are not already using it. In your YAML file, this would look something like network_mode: host. If you use the Synology UI, there should be a checkbox to "Use the same network as Docker Host".
Step 4: Check Synology Firewall
Even if it was working before, an update can sometimes reset things.
Go to your Synology Control Panel > Security > Firewall.
If the firewall is enabled, ensure you have rules that Allow traffic for:
TCP Port 8096
UDP Port 1900
UDP Port 7359 (good to have)
Step 5: Reboot Client Devices
Once you have reconfigured Jellyfin and restarted the container, reboot your Blu-ray player and your iPhone. This will force them to clear their network cache and search for the DLNA server again.
Summary of Actions
Primary Action: Go to the Jellyfin Dashboard > Networking and explicitly set the "Bind to local network address" to 192.168.1.253.
Secondary Action: Check your container's network mode. Change it to host for the most reliable DLNA performance.
Verification: Check your Synology Firewall settings.
Final Step: Restart the Jellyfin container and then reboot your client devices.
After performing these steps, check the new Jellyfin log file. You should consistently see it binding to and registering DLNA on 192.168.1.253. At this point, your devices should be able to discover and connect to the server.
If you continue to have issues, please feel free to share your YAML script (be sure to remove any sensitive information). https://vccgenerator.top/
Let's break down the problem and the solution.
Analysis of Your Jellyfin Log
The log file is very helpful. Here are the most important findings:
The DLNA "Connection refused" Error:
This is the most prominent error in your log:
[ERR] Jellyfin.Plugin.Dlna.Main.DlnaHost: Error updating device info for "BDP-S6700"
System.Net.Http.HttpRequestException: Connection refused (192.168.1.55:52323)
---> System.Net.Sockets.SocketException (111): Connection refused
This error means that your Jellyfin server (192.168.1.253) tried to connect to your Blu-ray player (192.168.1.55) on port 52323, but the Blu-ray player actively refused the connection. This is part of the DLNA protocol where the server tries to get more information from the client. While this error is present, it might be a symptom of a larger networking issue rather than the root cause.
The Network Binding Instability:
This is the most critical issue. I can see in your logs that the Jellyfin server was restarted multiple times, and its network binding changed.
Good Configuration (at 18:10 and earlier):
[INF] Jellyfin.Networking.Manager.NetworkManager: Bind Addresses ["192.168.1.253"]
[INF] Jellyfin.Plugin.Dlna.Main.DlnaHost: Registering publisher for "urn:schemas-upnp-org:device:MediaServer:1" on "192.168.1.253"
Here, Jellyfin correctly binds to your NAS's specific IP address and advertises its DLNA service on that address. This is what you want.
Bad Configuration (at 18:19 and 18:27):
[INF] Jellyfin.Networking.Manager.NetworkManager: Bind Addresses ["0.0.0.0"]
[INF] Jellyfin.Plugin.Dlna.Main.DlnaHost: Registering publisher for "urn:schemas-upnp-org:device:MediaServer:1" on "127.0.0.1"
This is a major problem. 127.0.0.1 is the "localhost" address, meaning the server is advertising itself only to itself. Your Blu-ray player and iPhone will never see the DLNA server if it's advertised on this address.
Why Linux Works but iPhone/DLNA Fails:
You can connect from your Linux machine because you are likely using a web browser and navigating directly to http://192.168.1.253:8096. This is a direct connection and doesn't rely on network discovery.
DLNA clients (like your Blu-ray player) and the Jellyfin mobile apps rely on a discovery protocol called SSDP, which uses UDP broadcasts on the network. If the server is misconfigured to advertise itself on the wrong IP, discovery fails, and the clients won't find the server.
The constant restarts and changing network bindings suggest there might be an issue with how the networking is configured either in the Jellyfin dashboard or in the container's environment/YAML file, which might have been affected by the 10.10.7 update.
How to Fix It: A Step-by-Step Guide
Let's walk through the steps to stabilize your network configuration and get your devices connected again.
Step 1: Check Jellyfin Network Settings
The easiest place to start is inside the Jellyfin web interface.
Access your Jellyfin server from your Linux machine's web browser (http://192.168.1.253:8096).
Navigate to Dashboard > Networking.
Check the following settings:
Bind to local network address: This is the most important setting. Do not leave it blank. Select your NAS's IP address (192.168.1.253) from the dropdown menu. This will force Jellyfin to use the correct network interface.
Local HTTP port number: Ensure this is set to 8096.
Published Server URL: Ensure this is set to http://192.168.1.253:8096
Scroll down and click Save.
Restart the Jellyfin container from the Synology Container Manager.
Step 2: Check Jellyfin DLNA Settings
In the Jellyfin Dashboard, go to Dashboard > DLNA.
Ensure that Enable DLNA is checked.
You can leave the other settings at their defaults for now.
Click Save.
Step 3: Verify Container Network Mode (Crucial for DLNA)
DLNA's discovery protocol (SSDP) can be tricky with Docker's default bridge network mode.
Recommended: host network mode. For services like Jellyfin that rely on network discovery, using the host network is much more reliable. It makes the container share the network stack of your Synology NAS, eliminating any issues with port mapping or broadcast traffic.
Alternative: bridge network mode. If you must use bridge mode, you need to ensure you have correctly mapped the necessary ports in your YAML file or Container Manager settings:
8096:8096/tcp (for the web interface)
1900:1900/udp (for DLNA/SSDP discovery)
You may also need to map port 7359/udp for client discovery.
I strongly recommend switching to host networking if you are not already using it. In your YAML file, this would look something like network_mode: host. If you use the Synology UI, there should be a checkbox to "Use the same network as Docker Host".
Step 4: Check Synology Firewall
Even if it was working before, an update can sometimes reset things.
Go to your Synology Control Panel > Security > Firewall.
If the firewall is enabled, ensure you have rules that Allow traffic for:
TCP Port 8096
UDP Port 1900
UDP Port 7359 (good to have)
Step 5: Reboot Client Devices
Once you have reconfigured Jellyfin and restarted the container, reboot your Blu-ray player and your iPhone. This will force them to clear their network cache and search for the DLNA server again.
Summary of Actions
Primary Action: Go to the Jellyfin Dashboard > Networking and explicitly set the "Bind to local network address" to 192.168.1.253.
Secondary Action: Check your container's network mode. Change it to host for the most reliable DLNA performance.
Verification: Check your Synology Firewall settings.
Final Step: Restart the Jellyfin container and then reboot your client devices.
After performing these steps, check the new Jellyfin log file. You should consistently see it binding to and registering DLNA on 192.168.1.253. At this point, your devices should be able to discover and connect to the server.
If you continue to have issues, please feel free to share your YAML script (be sure to remove any sensitive information). https://vccgenerator.top/