Access Denied to Admin
Closed this issue · 8 comments
After configuring my npm to reflect authorization to ~^/auth-(.*), I was able to successfully deny access to my Sonarr subdomain from the general public. However, even after logging in to my admin account, I am still denied access.
Confirmed that the Sonarr tab is configured for admin group. Used the following npm entries for my subdomain:
Your location block is wrong. It should be ~ ^/auth-(.*) (note the space... it's important)
Your location block is wrong. It should be
~ ^/auth-(.*)(note the space... it's important)
The exact way you typed it broke my subdomain completely, but adding the space into my original entry absolutely solved this problem - thank you!
Your location block is wrong. It should be
~ ^/auth-(.*)(note the space... it's important)The exact way you typed it broke my subdomain completely, but adding the space into my original entry absolutely solved this problem - thank you!
Yup, sorry... was half asleep and mixed up the first two characters and had to edit it to fix it lol
I hate to re-open this- but now, trying to duplicate this setup with Radarr, I am having the same issue where access is denied to admin. I triple checked the npm config and it is identical to the Sonarr one, save for the port being different in the api address. I have cleared cache, restarted dockers, and tried a different browser. Not sure why it wouldn't work, as it is still working fine for Sonarr :(
Do you have the block common exploits enabled? That has been known to break it in the past
Yup, just tried that as well, followed by the clear cache/restart docker/login and log out process. I even deleted and re-added the Radarr tab. I am really confused as to why Sonarr would be fine now and Radarr would not work, considering I just copy and pasted the config over from Sonarr (minus the api port for Radarr)
Edit: Additionally, I just realized that Sonarr is not really working - I missed this before, but although it lets me onto the page, none of my series information is loaded. It's like a blank profile. But when I access it from unRAID web UI, all the info is still there. What a mess.
Sorted out - I had api/v2/auth/$1 instead of api/v2/auth?group=$1
Also, had to remove the /api address entirely in order to get my library to show up.
All good now.
api/v2/auth/$1 should have worked too tho