Open 2t9z16yo opened 1 month ago
It's not clear if this is a bug or an environment issue, since this is working for a lot of people. To simplify the setup, did you try without direct connection (i.e. with direct connection disabled)?
that didnt make a difference either. i chose the disable direct connection option, restarted JD and tried using the extension to send a link to JD. still the same behaviour
Did you try different browsers (e.g. Firefox, Chrome) with the extension ? Also, is the problem occurs with different download services?
You can also try to open a support ticket here: https://support.jdownloader.org.
thanks! i tried firefox and it works - both with and without direct. any idea what i can do to fix this in Chrome/Arc? post on jdownloader support?
Yes, posting on the forum or opening a support ticket is your best choice, since the problem seems related to the browser plugin itself.
Current Behavior
I run jdownloader container on a synology using Container manager. Recently I added the mydownloader extension to Chrome/Arc.
Both the extension and container show connected to my myjdownloader account. When the extension opens the myjdownloader webpage, I see the download history from my jdownloader container.
I've also added the Custom Device IPs and Direct Connection Mode settings.
When I copy a link, the extension window opens. I select to download, and a large checkmark appears, confirming the link is sent. Yet in the jdownloader2 UI, there is no new activity.
port 3129 is open on synology firewall and forwarded on the router.
Expected Behavior
When I copy a link, the extension window opens. I select to download, and a large checkmark appears, confirming the link is sent. The item shows up in jDownloader linkgrabber
Steps To Reproduce
see above
Environment
Container creation
services: jdownloader: image: jlesage/jdownloader-2:latest container_name: jdownloader environment:
Container log
Container inspect
Anything else?
We previously had Issue 198 that was the exact same issue. But that issue was closed by the user; the bug was never fixed