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.
![[Image: attachment.php?aid=5082]](https://forum.jellyfin.org/attachment.php?aid=5082)
![[Image: attachment.php?aid=5083]](https://forum.jellyfin.org/attachment.php?aid=5083)
![[Image: attachment.php?aid=5084]](https://forum.jellyfin.org/attachment.php?aid=5084)
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.
Jellyfin 10.10.3 (Docker)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)