No longer able to access server - 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: No longer able to access server (/t-no-longer-able-to-access-server)

No longer able to access server - ajm2022 - 2024-11-17 Hello everyone, I'm very much a noob at this sort of thing, so please forgive me if this is an ignorant/dumb thread. I'll do my best to provide all the info I can upfront. I've been running Jellyfin on an OMV home server I set up several months ago using some old parts I had lying around. I have Jellyfin running in Docker Compose. I access this server exclusively on my home network, either via the browser interface on my Windows 10 PC, the Swiftfin client on my iPhone, or the Jellyfin app for my AppleTV.  Since it's pretty much just me using it, I usually turn the machine off when I'm done using it. Since I do not have static IPs set up, every time I rebooted the server I would have to use a new IP to access Jellyfin (or anything else on the server). After some searching around online, I discovered that I can use the server's hostname instead of typing out the IP. My server's hostname is "openmediavault," so for example I started accessing the OMV web interface via the url "openmediavault.local." Yesterday, I figured I could do the same thing with Jellyfin to avoid having to change the IP address every time I want to connect to it (i.e. use "openmediavault:8096" instead of "http://192.168.12.82:8096"). This worked perfectly until I updated OMV yesterday and rebooted the machine. Ever since, I have been completely unable to access Jellyfin on every client I've tried. Web browser (on my iPhone and my Windows PC), Windows 10 desktop client, iOS Swiftfin client, and AppleTV Jellyfin client all do not work. I can access the OMV browser interface and my other Docker Compose software (MakeMKV) just fine. Every time I attempt to connect, using either the hostname or the IP itself, I receive the same error message: "Connection Failure We're unable to connect to the selected server right now. Please ensure it is running and try again." I tried enabling the other 3 ports in my docker compose file 8920, 7359, and 1900 to see if maybe auto detection would work. On my appleTV, the server does show up under Local servers as "openmediavault:8096" but I still cannot connect to it.] I've also tried adding "JELLYFIN_PublishedServerUrl=openmediavault:8096" under environment in the compose file, but this hasn't helped either. I can only think of two things which may have caused this. 1) the OMV update or 2) messing around with the Jellyfin network settings. I don't 100% remember, but I believe I may have enabled IPv6 and also possibly put something in the "BaseURL" field, but I cannot access the dashboard anymore to check. My docker compose jellyfin log can be found at the below pastebin link: https://pastebin.com/MkLsnwgN Jellyfin Version: 10.9.11 (running in Docker Compose on my OMV server) OS: Linux Debian (OpenMediaVault version 7.4.13-1) Current server IP: 192.168.12.82 Thanks for any help. RE: No longer able to access server - TheDreadPirate - 2024-11-17 Can you share the contents of /config/config/network.xml? RE: No longer able to access server - ajm2022 - 2024-11-17 Hi, please see below. " <?xml version="1.0" encoding="utf-8"?> <NetworkConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <BaseUrl /> <EnableHttps>false</EnableHttps> <RequireHttps>false</RequireHttps> <InternalHttpPort>8096</InternalHttpPort> <InternalHttpsPort>8920</InternalHttpsPort> <PublicHttpPort>8096</PublicHttpPort> <PublicHttpsPort>8920</PublicHttpsPort> <AutoDiscovery>true</AutoDiscovery> <EnableUPnP>false</EnableUPnP> <EnableIPv4>true</EnableIPv4> <EnableIPv6>true</EnableIPv6> <EnableRemoteAccess>false</EnableRemoteAccess> <LocalNetworkSubnets /> <LocalNetworkAddresses /> <KnownProxies /> <IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces> <VirtualInterfaceNames> <string>veth</string> </VirtualInterfaceNames> <EnablePublishedServerUriByRequest>false</EnablePublishedServerUriByRequest> <PublishedServerUriBySubnet /> <RemoteIPFilter /> <IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist> </NetworkConfiguration> " RE: No longer able to access server - TheDreadPirate - 2024-11-18 And your docker config for Jellyfin? RE: No longer able to access server - ajm2022 - 2024-11-18 Here it is: " services: jellyfin: image: lscr.io/linuxserver/jellyfin:latest container_name: jellyfin environment: - PUID=1000 - PGID=100 - TZ=Etc/UTC - JELLYFIN_PublishedServerUrl=openmediavault:8096 volumes: - /config/jellyfinconfig - /srv/dev-disk-by-uuid-207d4c19-962f-408a-8d4c-991b6ac59cad/media/Showsdata/tvshows - /srv/dev-disk-by-uuid-207d4c19-962f-408a-8d4c-991b6ac59cad/media/Moviesdata/movies ports: - 8096:8096 - 8920:8920 #optional - 7359:7359/udp #optional - 1900:1900/udp #optional restart: unless-stopped " RE: No longer able to access server - TheDreadPirate - 2024-11-18 Remove the published server url. I don't THINK that is the problem, but what you were trying to do that settings doesn't do. If you want all your clients to use "openmediavault" you need to set your actual server's hostname to be that. You could also set a static IP and then set the router to respond to that host name with the static IP. RE: No longer able to access server - ajm2022 - 2024-11-18 I removed the published server URL but it still doesn't work. Just double checked and under network my server's hostname is set to "openmediavault".