2025-01-08, 07:57 AM
Sure! https://pastebin.com/Zm4pymi2
I used the one from yesterday, since there is more info
I used the one from yesterday, since there is more info
2025-01-08, 07:57 AM
Sure! https://pastebin.com/Zm4pymi2
I used the one from yesterday, since there is more info
2025-01-08, 01:43 PM
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.
2025-01-08, 02:08 PM
(This post was last modified: 2025-01-08, 02:18 PM by xyz1234. Edited 2 times in total.)
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
2025-01-08, 02:19 PM
(This post was last modified: 2025-01-08, 02:19 PM by TheDreadPirate.)
/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/
2025-01-08, 02:41 PM
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
2025-01-18, 08:40 AM
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:
Code: {
2025-01-18, 07:32 PM
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. |
|
|