-
Notifications
You must be signed in to change notification settings - Fork 7
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
Does this still work? #5
Comments
Unfortunately no with DSM7, I had sent a mail to synology support, they claim they are aware of the issue and will take a look, but it was few months ago and no feedback yet. It seems it affects all the DLM plugins. |
Tested with last version of DSM 7 (7.1 Beta 4) and now it works. I have to restart Download Station, but after restart it works fine |
Can't make it work. I use macvlan, but container is accessible from host via internal bridge network: This is a piece of log file from Jackett debug: https://pastebin.com/Bjdc8e66 I do not know what to do, Jackett itself works correctly, i can't understand is it a networking problem or plugin one. |
I've made some more investigations. One of the problem was unstable FlareSolverr so i've deploiyed 3.0.0_beta3. I make a build from sourcecode and this 2 actions made login possible. Now, if i use the link from source code and make It's DSM 7.1 and Download Station 3.9.3-4609. |
Installed one more instance of Jackett v0.20.2297 using SynoCommunity store. Reconfigured addon. Restarted Download Station. It works! Seems like it's some Docker-related problem |
dsm 7.2 all work fine. |
How do you configure? I have Jackett in Docker the same with host. |
First, I would check that the Jackett web interface opens in your browser at http://localhost:9117 or your local ip:9117 |
Username: |
|
It worked with localhost:9117 now. I must restart Download Station for dlm working. |
I can't seem to add it to Download Station in DSM 6 or 7. Got two Jackett servers running and neither will add. Following the instructions given but I want to check if it is now unsupported.
The text was updated successfully, but these errors were encountered: