2025-02-19, 05:06 PM
Servers local network is fine, all the other services running at the time reported no errors and no logs on the router to say if the port had any issues or was dropped.
The docker (official) is created by the command line using "docker run -d -p 8096:8096 --name jelly --privileged --group-add="106" --device /dev/dri/renderD128
dev/dri/renderD128 --device /dev/dri/card0dev/dri/card0" and then a bunch of mount points for storage, so i don't think this is an issue either. No proxy server is being used.
If the server lost connection to the client (uk>usa) then that could give the "no route to host" issue, but it shouldn't be allowed to bring down jellyfin.
The docker (official) is created by the command line using "docker run -d -p 8096:8096 --name jelly --privileged --group-add="106" --device /dev/dri/renderD128
dev/dri/renderD128 --device /dev/dri/card0dev/dri/card0" and then a bunch of mount points for storage, so i don't think this is an issue either. No proxy server is being used.If the server lost connection to the client (uk>usa) then that could give the "no route to host" issue, but it shouldn't be allowed to bring down jellyfin.