What changed with how Sonarr works with reverse proxies?

Help & Support
#1

Sonarr version (exact version): 4.0.0.425
Mono version (if Sonarr is not running on Windows): .Net 6.0.13
OS: Docker
Debug logs: N/A
Description of issue:
18mths ago Radarr changed from Nancy to AspNetCore, and I had to change my nginx config - [BUG]: 4.0.0.5371 breaks nginx reverse proxy · Issue #6676 · Radarr/Radarr · GitHub.

Some time after that the same happened with Sonarr. However, seemingly a few months ago (I’m only realising now that my config had reset, so I’m not sure when exactly) something changed and the default setup works fine again.

I’m looking to find out what it was and then see if Radarr would make the same change.

Ta!

#2

The v4 beta uses AspNetCore, that’s the only recent change.

#3

Ta.

Just opened Radarr and Sonarr in a different browser, turns out Sonarr hasn’t been magically fixed for the default nginx config.

Although, that means that my browser is weirdly caching something for Sonarr that it isn’t for Radarr. The mystery continues!

#4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.