-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
[BUG] NZBGet pass error #78
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
This looks like an app issue, not a container issue. I would recommend seeking support from lazylibrarian github/devs. |
I actually just fixed it. But it will actually be a problem for everyone since its in the source. If anyone else has this issue, you can fix it by ssh or run docker commands like so
Then change (for me) line 7661. Pasting the entire expose for nzbget
To this
Then run
Lastly
Pass on line 7661 needs to be pwd. |
This then should be reported upstream. |
for sure. I don't have a gitlab so I guess I will need to make one lol Edit: https://gitlab.com/LazyLibrarian/LazyLibrarian/-/issues/2643 |
This should be good now https://gitlab.com/LazyLibrarian/LazyLibrarian/-/commit/db937bebcad3178cae3717bb69ad3e30654a6443 |
Is there an existing issue for this?
Current Behavior
Installing docker using supplied compose and sets everything up fine but when testing connection to nzbget nothing shows up. Opening f12 (dev tools) shows and error 500 when hitting the test. Manually navigating to the test page shows
500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
NZBGet works fine across radarr, sonarr, lidarr, readarr and others.
Expected Behavior
Insert nzbget info and test connection successfull.
Steps To Reproduce
Install via docker compose
Change settings/downloaders and hit test nzbget
Connection shows successfull.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: