Closed BassMatt closed 3 months ago
Isn't basic browser pop up auth method not recommended anymore on sonarr and only forms (login page) is. You can use the latter and have a proper more secure auth and still be able to call the api.
Apologies, got some more context.
My radarr/sonarr are hosted behind nginx, and it requires basic auth to forward the requests to the servarr instances - similar to the person from that other thread using cloudflare zero trust.
I'll need to pass the headers regardless of the servarr instances using basic or form auth on their end to connect.
Apologies, got some more context.
My radarr/sonarr are hosted behind nginx, and it requires basic auth to forward the requests to the servarr instances - similar to the person from that other thread using cloudflare zero trust.
I'll need to pass the headers regardless of the servarr instances using basic or form auth on their end to connect.
Oh. Is that a like some seedbox/service provider thing that they add a basic auth or manually added?
Yeah, exactly. For my case I'm using a seedbox provider that has the nginx proxy setup and I don't have control to change.
I have this same issue. For me it's all hosted internally, but Jellyseerr lives on my DMZ and radarr/sonarr are internal. I am unable to connect to them as they need header auth.
If you have a basic auth, I think it will work using your url as:
http://user:password@domain.com
As basic auth supports passing in the user and pass in the url
(A user in discord tried it as well: https://discord.com/channels/952656177924300932/1244815845834752020/1245179633733992518)
So I will be closing this issue. Feel free to re-open if you can't get it to work
Description
Hey all, I'm trying to setup a connection with my radarr/sonarr instance.
I am hosting jellyseerr on my LAN. However, both my radarr/sonarr are outside of my LAN. To establish a connection it seems I have to pass a Basic Authentication header as well as the API key. I'm able to do this using https://docs.lunasea.app/, and removing the basic auth header messes up the connection.
It also seems like this is a common issue with overseerr as well. https://github.com/sct/overseerr/issues/3425
Desired Behavior
When adding a new radarr/sonarr server, jellyseerr should add a field in the configuration settings to add Custom Headers to the request (e.g. Basic Auth headers).
Additional Context
No response
Code of Conduct