-
-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nzb Download Link incorrect for Sonarr #71
Comments
could not reproduce this with some quick testing: every test confirmed prowlarr will use exactly what the user inputs. Also looks like you removed the most important part of bug reports from your post.
to be clear: you're entering: any proxy settings? screenshot & trace logs to confirm? (Reminder to clip or block out the API key for screenshots) |
Sorry for not including the trace report, i was on mobile at the time and wasn't able to get it - but wanted to get it submitted so it was able to be seen. to be clear: you're entering: prowlarr.domain.com as the Prowlarr URL in the application settings and then in the logs that is turning into prowlarr.domain.com:9696 being sent to the app ? Yes that is correct - the logs are on Sonarr, not Prowlarr to clarify - Wasn't sure if to post it here or on Sonarr, as a bug as it is directly related Sonarr Indexer Setting Prowlarr Application Setting (There is other errors in there as i ran up another instance to quickly test with) incase it was an issue with my sonarr - But Line 3058 is what i was talking about. |
Full disclosure, on mobile so can't see actual line numbers, but a review of those sonarr logs seems to indicate the indexers are added just fine. And are correctly at the subdomain without the port, as matches your screenshot. Prowlarr Server Input for Sonarr (I'll assume typos and inaccurate obfuscation on your screenshot) so that matches sonarr's logs for the indexers. regardless, I see no instances of the port being mysteriously appended in that log? |
Yeah no problem, that's why i didn't include it originally - was a bit difficult. On line 3058 21-5-25 10:36:42.9|Trace|HttpClient|Req: [GET] http://indexers.example.com.au:9696/1/download?apikey=(removed)&link=OHBDMjIxTGI0cHRrdVdpRGdSTVpMSlg4U1p1NlBld0lmMEdqaURvTmhYS21JRE00ZGNjQ0NvS09aUlVvRit2U3JzdCtGQUVKS2YvSk1PQ1g0elpIVEhuWGhxM01UOFF1Mmd3d3NRRVF2QzZyYlNnTklMY1BCSU1Rc3BDMWluem5DUWF5WFNFekdlOFl1dzI3ZWV6akRzcFdJc3VJNklRekUrVCtMbEVsT1JJPQ&file=24.S08E03.1080p.BluRay.X264-AVCDVD After this occurs in the logs, it fails to fetch the nzb. |
Relevant Log snip from sonarr in this case we should not have the port and should probably be using the same prowlarr url the app config is set
|
Describe the bug
Upon adding an application and setting the Prowlarr Server without a port if using as reverse proxy.
e.g entering radarr.domain.com it automatically appends the port resulting in radarr.domain.com:9696 and when it queries the download of the nzb/torrent fails
[v3.0.6.1196] System.Net.WebException: The operation has timed out.: 'http://prowlarr.domain.com.au:9696/4/download?apikey=(removed)' ---> System.Net.WebException: The operation has timed out.
To Reproduce
Expected behavior
It should not append the :9696 as it is behind a reverse proxy.
Platform Information (please complete the following information):
I haven't submitted a bug report on Github before for anything, so let me know if anything is incorrect or if more info is needed.
I know this is a very early version of Prowlarr, so this will probably pop up / if it hasn't already.
The text was updated successfully, but these errors were encountered: