whauk

Figured it out - I had two problems and only one of them was in front of the keyboard. 1. jDownloader uses internally port 5800 for the web UI which I mapped to 7807. Since Q24 says you should remove all ports form the "Container to route through the VPN" I did exactly that - which made the jDownloader container use its internal fallback. And I continued to refer to my (now non-existent) remapped port in the qbt container configuration... 2. The Web UI of the container that now additionally runs though the VPN now needs to be accessed through the "non conflicting port number for 'Host Port'". It would be helpful if A24 mentioned that in order to save idiots like myself additional unnecessary confusion. Thank you. docker run.txt supervisord.log

Thanks, supervisord.log see attached. Not sure about the docker run command though - how do I get to that if I just use Unraid's GUI in order to start and stop the container? supervisord.log

Ok, that seems to be a misunderstanding. The qbit container does not have a separate IP - the NAS has a local IP. I differentiate containers only by port nos. If I address the qbit container by its port no. I get the web UI of the qbit client. If I address the jDownloader container by its Web UI port no. I get an error message.

Thanks again, that's also what I did. How about accessing the Web UI? From within my LAN it's still http://local_IP:Web_UI_port_no.?

Thanks, that is what I did. And about the "Host port" - any port no. will do? And I can still access the NAS with http://local_IP:Web_UI_port_no.?

I only just now learned that one can run containers through other containers' VPN and tried it with jDownloader following the instructions given at https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md, Q24 and Q4. Result is the container works flawlessly and I can manage it through myjDownloader.org but I can't access the Web UI locally. Assuming that I don't really understand the principle behind it, I am uncertain whether the "any non conflicting port number" in "Enter in the applications Web UI port for 'Container port' from your list taken earlier in step 4. above and any non conflicting port number for 'Host Port' (host port must not be used by another container)." actually means that I should use any wild port no. that is not in use on the NAS so far? And would it have to reappear somewhere else? Would I use the "Container port" or the "Host port" to access the jDonwloader Web UI? Also I am uncertain how to make sure I follow Note 1 (if relevant).

Thank you, absolutely correct - in other browsers that I did not suffocate in plugins everything works fine. Will have to find out, which one kills the containers. Thanks a lot!

Since this morning the WebUI of jdownloader2 shows this error message: "TypeError: WeakMap key undefined must be an object or an unregistered symbol executeCommands@http://xxx.xxx.x.x:xxxx/:529:36 commandsListener@http://xxx.xxx.x.x:xxxx/:652:32" My krusader interface shows a similar message, so that I assume that the error message has something to do with VNC (especially so as all my other containers that - afaik - do not use VNC run without any problem). Has anyone encountered the same or a similar problem and knows anything about solutions? Any help will be much appreciated.

I have the same problem with downloads - it may be because I do not seed *that* much. After a while I have the impression as though my qBT container silently goes to sleep - doesn't see any sources anymore. A reboot briefly remedies the situation but after a day or two, at best after a couple of days, the situation is as it was. I already deleted the container and set it up from scratch again but the situation quickly went to where it was before. i wonder whether this is just two sides of the same problem.

Slightly OT: Is there a HowTo somewhere how to go about connecting to all your containers using SSL? Somehow I don't seem to be able to makle it work.

https://<ip>/<DynDNS address>:port + Login/PW

Thanks, but I do not use a proxy server, Privoxy or otherwise and Jackett neither. My current understanding is that A26 wouldn't solve my problem, correct?

I know it's OT, but have to ask anyway since Transdroid has been discussed here previously: My Transdroid client now completely stopped working with qbt 4.3.3. After installing the TD interim version (as a result of the breaks in in qbt 4.2.0) from time to time the error message "Access denied (Please check your settings)" appeared. Brief reload (pulling screen down) and everything worked fine again until the next time. Now (for about two days or so) the reload does not work anymore. Has anyone experienced anything similar? I am on Unraid 6.90, qbt 4.3.3 and TD 2.5.19. Thanks, everyone.

Oh yes, I would very much like to second this!

Strange thing - I had a hunch and exchanged the Nord VPN conf file for a newer one (just swapped them) and restarted the container. Everything hunky dory.