|
#1
|
|||
|
|||
Jdownloader connect with VPN with Docker
Hi,
I am using these two images within Docker: **External links are only visible to Support Staff****External links are only visible to Support Staff** **External links are only visible to Support Staff****External links are only visible to Support Staff** Jdownloader is connected with the internet with the VPN connection from my VPN provider Ivacy. Jdownloader establishes the connection via Docker > Network > Container > deluge-openvpn. My Ivacy credentials, server and so one are set in the deluge-openvpn container. This works like it should and download speed is not bad, but even if the download speed is quite fast from my vpn connection, I still don't get it, why the WebUI at my JDownloader is really really slow, sometimes I even have to make some attemps to access it. How can I solve this? Or which other options do I have instead of the deluge-openvpn container? Is a Jdownloader vpn plugin available, which handles this more easily? Update: I see the jdownloader forum censors the links :-/ The jdownloader container is from jaymoulin, the deluge-openvpn container is from dynomitecentral Last edited by FalconX; 18.04.2020 at 13:48. |
#2
|
||||
|
||||
yes all urls except whitelisted domains get blocked for everyone but support staff.
are you accessing via LAN it should only authenticate over my.jdownloader and switch to lan connection for communication after that. If everything else is over wan and then vpn it will increase latency vs direct connect from your installation to your client via my.jd servers. jd <> vpn <> my.jd <> mobile device jd <> vpn <> my.jd <> vpn <> mobile device jd <> my.jd <> mobile device the docker supporter does have information about setting up direct connection. more vpn connections you have the slower and higher latency you'll experience.
__________________
raztoki @ jDownloader reporter/developer http://svn.jdownloader.org/users/170 Don't fight the system, use it to your advantage. :] Last edited by raztoki; 18.04.2020 at 15:50. |
#3
|
|||
|
|||
Found the solution now, forwarding the port 3219 for the direct connection in the VPN container did the trick.
It's still not that fast than pyload, but it's good :-) |
Thread Tools | |
Display Modes | |
|
|