31 minutes ago
(This post was last modified: 28 minutes ago by counternihilist. Edited 1 time in total.)
Brief description of my setup:
Running Jellyfin 10.11.3.r01 in a Docker (28.1.1.r54) container on an Asustor AS5304T NAS at internal IP 192.168.1.154, just updated to current version last night
Because of constraints on the Asustor unit, port numbers are 28920/28096 instead of 8920/8096 (I am appending :28920 on server address in all my apps)
I access through a public URL via Dynamic DNS from a shared webhost account on Greengeeks through a domain name I own
The primary endpoint is my home Linux server at internal IP 192.168.1.153, running Apache 2.4.65-4 on a Manjaro system, Linux Kernel 6.16.8-1 if that matters (the Apache configuration redirects from /jellyfin to the NAS IP at port 28920). I host a bunch of bare-metal apps there plus an LDAP server for centralized authentication, which Jellyfin uses
I have port forwarding rules for ports 28920/28096 to 192.154.1.154 on my Netgear Nighthawk RS200 router on a Verizon FiOS connection
I do NOT have a reverse proxy set up, considering migrating later but haven't worked out how it'll impact the rest of my apps. I have one subdomain I use for all of them, with URL paths or port numbers differentiating the webapps.
Anyway, I recently purchased a new Sectigo SSL certificate through Namecheap to replace my expiring one, converted my .crt and .key to .pfx via openssl (did not include a root certificate since that hasn't been necessary in the past) and installed in the Jellyfin config directory. At the same time as replacing the certificate I also initiated an update to the current version (don't remember the previous version number it was at).
After the server and cert upgrade, everything looks fine from the web browser, both on LAN and local wifi. I had issues before with same-origin access but still have my domain and IP registered in my /etc/hosts file on the main server at .153, so no issue there. DDNS, main server and Jellyfin all on the same cert.
Most (but not all) of my Android apps, however, are getting an "Unable to reach server" error. Here's a list of their current states:
Samsung Galaxy Tablet (Jellyfin client 2.6.3) on local wifi - Works fine
Motorola Edge 2020 (running LineageOS) (Jellyfin client 2.6.3) - Does not connect *except very occasionally*, will immediately lose connection and not reconnect if I close the app, web access works fine through browser. Have tried both on and off local wifi, and internal NAS IP while on local wifi, does not help.
Android TV - Would not connect for hours, then suddenly connected, has maintained connection ever since
Android TV in bedroom - Will not connect at all
Have rebooted the Apache server on .153, Docker and Jellyfin on the .154 NAS multiple times, even rebooted the router.
I am not seeing anything terribly helpful in the Jellyfin logs, and no relevent entries in the router or apache logs. Here's a sample of Jellyfin's logs since the last reboot, with multiple failed access attempts:
UPDATE: Just remembered to include the fact that on every mobile/TV device that's been having issues, I've been force stopping, clearing cache and data, and even rebooting the device, still having the same issue.
Running Jellyfin 10.11.3.r01 in a Docker (28.1.1.r54) container on an Asustor AS5304T NAS at internal IP 192.168.1.154, just updated to current version last night
Because of constraints on the Asustor unit, port numbers are 28920/28096 instead of 8920/8096 (I am appending :28920 on server address in all my apps)
I access through a public URL via Dynamic DNS from a shared webhost account on Greengeeks through a domain name I own
The primary endpoint is my home Linux server at internal IP 192.168.1.153, running Apache 2.4.65-4 on a Manjaro system, Linux Kernel 6.16.8-1 if that matters (the Apache configuration redirects from /jellyfin to the NAS IP at port 28920). I host a bunch of bare-metal apps there plus an LDAP server for centralized authentication, which Jellyfin uses
I have port forwarding rules for ports 28920/28096 to 192.154.1.154 on my Netgear Nighthawk RS200 router on a Verizon FiOS connection
I do NOT have a reverse proxy set up, considering migrating later but haven't worked out how it'll impact the rest of my apps. I have one subdomain I use for all of them, with URL paths or port numbers differentiating the webapps.
Anyway, I recently purchased a new Sectigo SSL certificate through Namecheap to replace my expiring one, converted my .crt and .key to .pfx via openssl (did not include a root certificate since that hasn't been necessary in the past) and installed in the Jellyfin config directory. At the same time as replacing the certificate I also initiated an update to the current version (don't remember the previous version number it was at).
After the server and cert upgrade, everything looks fine from the web browser, both on LAN and local wifi. I had issues before with same-origin access but still have my domain and IP registered in my /etc/hosts file on the main server at .153, so no issue there. DDNS, main server and Jellyfin all on the same cert.
Most (but not all) of my Android apps, however, are getting an "Unable to reach server" error. Here's a list of their current states:
Samsung Galaxy Tablet (Jellyfin client 2.6.3) on local wifi - Works fine
Motorola Edge 2020 (running LineageOS) (Jellyfin client 2.6.3) - Does not connect *except very occasionally*, will immediately lose connection and not reconnect if I close the app, web access works fine through browser. Have tried both on and off local wifi, and internal NAS IP while on local wifi, does not help.
Android TV - Would not connect for hours, then suddenly connected, has maintained connection ever since
Android TV in bedroom - Will not connect at all
Have rebooted the Apache server on .153, Docker and Jellyfin on the .154 NAS multiple times, even rebooted the router.
I am not seeing anything terribly helpful in the Jellyfin logs, and no relevent entries in the router or apache logs. Here's a sample of Jellyfin's logs since the last reboot, with multiple failed access attempts:
Code:
[2025-11-22 15:23:17.912 +00:00] [INF] [15] Emby.Server.Implementations.ApplicationHost: Core startup complete
[2025-11-22 15:23:17.912 +00:00] [INF] [15] Main: Startup complete 0:00:14.090263
[2025-11-22 15:23:21.238 +00:00] [INF] [12] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" request
[2025-11-22 15:23:26.321 +00:00] [INF] [15] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" closed
[2025-11-22 15:30:37.448 +00:00] [INF] [58] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" request
[2025-11-22 15:30:47.455 +00:00] [WRN] [67] Emby.Server.Implementations.HttpServer.WebSocketConnection: WS "my.public.ip.address" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake."
[2025-11-22 15:30:47.458 +00:00] [INF] [67] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" closed
[2025-11-22 16:12:24.685 +00:00] [INF] [79] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" request
[2025-11-22 16:12:34.057 +00:00] [INF] [69] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" closed
[2025-11-22 16:17:15.644 +00:00] [INF] [58] Jellyfin.Server.Implementations.Users.UserManager: Authentication request for "root" has succeeded.
[2025-11-22 16:17:15.645 +00:00] [INF] [58] Emby.Server.Implementations.Session.SessionManager: Current/Max sessions for user "root": 0/10
[2025-11-22 16:17:15.648 +00:00] [INF] [58] Emby.Server.Implementations.Session.SessionManager: Creating new access token for user 8b753d71-80fb-48c9-a6d0-934d46d0f4af
[2025-11-22 16:17:15.763 +00:00] [INF] [60] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" request
[2025-11-22 16:18:39.750 +00:00] [INF] [58] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" closed
[2025-11-22 16:18:40.171 +00:00] [INF] [64] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" request
[2025-11-22 16:19:07.866 +00:00] [INF] [67] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" closed
[2025-11-22 16:19:08.241 +00:00] [INF] [58] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" request
[2025-11-22 16:20:28.082 +00:00] [INF] [65] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" closed
[2025-11-22 16:20:28.428 +00:00] [INF] [84] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" request
[2025-11-22 16:21:14.733 +00:00] [INF] [42] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" request
[2025-11-22 16:21:34.706 +00:00] [INF] [81] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" closed
[2025-11-22 16:21:35.039 +00:00] [INF] [54] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" request
[2025-11-22 16:24:23.288 +00:00] [WRN] [74] Emby.Server.Implementations.HttpServer.WebSocketConnection: WS "my.public.ip.address" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake."
[2025-11-22 16:24:23.290 +00:00] [INF] [74] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" closed
[2025-11-22 16:24:25.497 +00:00] [INF] [74] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "my.public.ip.address" closedUPDATE: Just remembered to include the fact that on every mobile/TV device that's been having issues, I've been force stopping, clearing cache and data, and even rebooting the device, still having the same issue.