+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: Can't connect to selected server (/t-can-t-connect-to-selected-server)
RE: Can't connect to selected server - xyz1234 - 2025-01-08
Sure! https://pastebin.com/Zm4pymi2
I used the one from yesterday, since there is more info
RE: Can't connect to selected server - TheDreadPirate - 2025-01-08
It looks like the container does not have full read/write access to portions of /config. Make sure that the container owns and can r/w where /config is stored on the host.
RE: Can't connect to selected server - xyz1234 - 2025-01-08
Ah, I found the line you probably refer to. But unfortunately it seems, that this path does not exist:
System.IO.DirectoryNotFoundException: Could not find a part of the path '/config/root/default/Sammlungen'.
But this path does not exist on the host:
https://imgur.com/a/HUUI8Lg
But does that really impact the metadata synchronization and the pull/scan of the movie library?
PS: Assigning User "apps" full control permissions does not solve the issue
RE: Can't connect to selected server - TheDreadPirate - 2025-01-08
/config/root has all of your library configs. Without it, a lot of things will break. I'm surprised it runs at all.
Code:
chris@rat-trap:/docker/containers/jellyfin-prod-data/config$ ll root/default/
total 68
drwxr-xr-x 17 jellyfin chris 4096 Jan 1 19:36 ./
drwxr-xr-x 3 jellyfin chris 4096 Aug 15 2023 ../
drwxr-xr-x 2 jellyfin chris 4096 Oct 5 00:35 Anime/
drwxr-xr-x 2 jellyfin chris 4096 Oct 5 00:35 'Anime Movies'/
drwxr-xr-x 2 jellyfin chris 4096 Jun 6 2024 'Anime Music Videos'/
drwxr-xr-x 2 jellyfin chris 4096 Apr 28 2024 'Audio Books'/
drwxr-xr-x 2 jellyfin chris 4096 Dec 11 20:26 'Japanese and Korean Movies'/
drwxr-xr-x 2 jellyfin chris 4096 Oct 5 00:35 'Japanese Live Action Shows'/
drwxr-xr-x 2 jellyfin chris 4096 Oct 5 00:35 Movies/
drwxr-xr-x 2 jellyfin chris 4096 Jan 1 19:36 Music/
drwxr-xr-x 2 jellyfin chris 4096 Aug 15 2023 'Music Videos'/
drwxr-xr-x 2 jellyfin chris 4096 Aug 15 2023 'Old Time Radio'/
drwxr-xr-x 2 jellyfin chris 4096 Sep 10 17:37 Podcasts/
drwxr-xr-x 2 jellyfin chris 4096 Sep 9 19:26 'Recorded Movies'/
drwxr-xr-x 2 jellyfin chris 4096 Sep 9 19:26 'Recorded Shows'/
drwxr-xr-x 2 jellyfin chris 4096 Sep 9 19:26 Recordings/
drwxr-xr-x 2 jellyfin chris 4096 Oct 5 00:35 'TV Shows'/RE: Can't connect to selected server - xyz1234 - 2025-01-08
Seems to work again
Thank you very much @TheDreadPirate
I just had to add the folder "Sammlungen" (translated: collections) to the root/default folder
Then everything worked
RE: Can't connect to selected server - syize - 2025-01-18
I got the same error recently. Connecting to the server on the web page gives me the error, and my solution is delete the server, enter the url to add the same server again.
I have checked jellyfin's log. It doesn't have any output when this error occurs. However, when I check the response from the server in browser, there is a value called "LocalAddress" and its value is "http://127.0.0.1:8096". I have setup nginx reverse proxy for jellyfin and I always access jellyfin through the url I assign to it. Is this error related to the nginx reverse proxy? I access jellyfin in the same PC, so it couldn't be caused by the firewall.
Here is the information about jellyfin and the OS:
- Jellyfin: 10.10.3
- OS: Arch Linux
- response from jellyfin server in browser:
Code:
{
"LocalAddress": "http://127.0.0.1:8096",
"ServerName": "MSIArch",
"Version": "10.10.3",
"ProductName": "Jellyfin Server",
"OperatingSystem": "",
"Id": "1e6f1ad69781495699a6f5ba17934560",
"StartupWizardCompleted": true
}RE: Can't connect to selected server - TheDreadPirate - 2025-01-18
When using "localhost" or 127.0.0.1 to access Jellyfin you are not traversing the firewall. So being able to access Jellyfin with those addresses is not a valid test of your firewall configuration.
But the error you originally mentioned is USUALLY caused by browser caching. The "Id" file in the browser response is a unique ID generated when you install Jellyfin. If you reinstall Jellyfin on a host you had accessed in that browser, the cached ID will not match the new ID.
The proper solution is to clear your browser cache.