Seperate multi-instance local storage entries for Radarr instances running under the same host #9211

New issue

Closed

opened 2026-02-20 00:11:34 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 00:11:34 -05:00

Owner

Originally created by @eliasbenb on GitHub (Jun 28, 2025).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

This is a bug that was fixed in Sonarr last year. Original issue: https://github.com/Sonarr/Sonarr/issues/7368.

Please read the original issue for a more detailed explanation, but the TLDR version is that Radarr is storing the default/memoized data in localstorage under a radarr key, which causes conflicts if two Radarr instances are served with a reverse proxy under the same host but with different path prefixes.

Expected Behavior

There should be a separation between of localstorage keys for Radarr instances under different path prefixes.

Steps To Reproduce

Start Radarr instance A with root path /$a
Start Radarr instance B with root path /$b
Reverse proxy Radarr instances A and B under the same host (on path prefixes /$a and $/b)
Perform any operation that writes to the radarr localstorage key (e.g. adding a new movie through the UI)
Notice that the radarr localstorage key is overwritten for both instances

Environment

- OS: Ubuntu 24.04
- Radarr: 5.27.1.10112 (rev 71d0561)
- Docker Install: Yes
- Using Reverse Proxy: Yes
- Browser: FireFox 140.0.2 (64-bit)
- Database: N/A

What branch are you running?

Develop

Trace Logs? Not Optional

N/A, this is a frontend bug

Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @eliasbenb on GitHub (Jun 28, 2025). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Current Behavior This is a bug that was fixed in Sonarr last year. Original issue: https://github.com/Sonarr/Sonarr/issues/7368. Please read the original issue for a more detailed explanation, but the TLDR version is that Radarr is storing the default/memoized data in localstorage under a `radarr` key, which causes conflicts if two Radarr instances are served with a reverse proxy under the same host but with different path prefixes. ### Expected Behavior There should be a separation between of localstorage keys for Radarr instances under different path prefixes. ### Steps To Reproduce 1. Start Radarr instance A with root path `/$a` 2. Start Radarr instance B with root path `/$b` 3. Reverse proxy Radarr instances A and B under the same host (on path prefixes `/$a` and `$/b`) 4. Perform any operation that writes to the `radarr` localstorage key (e.g. adding a new movie through the UI) 5. Notice that the `radarr` localstorage key is overwritten for both instances ### Environment ```markdown - OS: Ubuntu 24.04 - Radarr: 5.27.1.10112 (rev 71d0561) - Docker Install: Yes - Using Reverse Proxy: Yes - Browser: FireFox 140.0.2 (64-bit) - Database: N/A ``` ### What branch are you running? Develop ### Trace Logs? **Not Optional** N/A, this is a frontend bug ### Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided. - [x] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.