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.

Since yesterday I cannot access the Web GUI anymore (after a restart of the container, no other changes). Does anyone else have the same problem?

Can someone please give me a couple of pointers how to set up the Duplicati container on an Unraid server to backup a couple of Win10 machines to a share on that same Unraid server? Somehow I can't figure out how to get to the Win10 machines in any way. Thanks in advance for any help.

Same here with NordVPN. A container restart temporarily sovles the problem - until next time.

Thanks for this, but I think the last line should read: "chown app:users /config/libs/sevenzipjbinding*" (?)

Now I have something: The downloads are still in sonarr's activity list but with a red x (physical remove from downloader) and a manikin beside it (for manual moving) and the logs show "...path \downloads not exitant or not accessible." 😣 It seems, I still do not understand the principle. I was at a point where I thought you can basically do anything you like, it must work as long as both variables (i.e. container paths) have the same name in both containers - in one container I achieved this by renaming the respective path from "/data" to "/downloads" - and both variables point to the same host path ("/mnt/user/Downloads"). OT: Does it make any difference (and if so, what) whether the path is "/mnt/user/Downloads" or "/mnt/cache/Downloads"? Thanks for your help.

Yes, I did. The path within the downloader is /downloads or downloads/incomplete respectively. Otherwise the client would just stall because the download path is non-existent/inaccessible. There is no error message, sonarr just does nothing. It initiates new downloads, though, which the download client puts in the /downloads directory. I don't quite get the point about the command prompt: When I open one in each container they show the same thing that Krusader shows: All's well, the downloads land in the correct path.

Apologies if i have to return to the question host path vs. container path. I have the following problem: The (container) path of my indexer is /downloads. The (container) path of my download client is /data. Both container paths are mapped to the same host path. Sonarr can't pick up the donloaded files because the container paths are not aligned. So I renamed the /data container path to /downloads in the container settings. Still nothing happening. Am I misunderstandiong anything?

Just as an aside for those of you that use Transdroid for connecting to your qbt client: You may have noticed that version 2.5.16 ceased to work due to the changes in qbt 4.20. There is an interim version to be found here - which unfortunately still produces an "Internal error building request" on my phone but it seems to work for others. Just saying. Edit: It works on my phones without a hitch, it just cannot be installed as an upgrade of V. 2.15.6.

Thanks - that almost does it. Unfortunately the application dialogue window in the current Firefox (71) wants to find either a locally or at least on a network drive installed Windows program to handle the magnet link. I found no way to have FF directly handle a magnet link directed to a docker container on an Unraid system. What works, though, is to register the qbt client with a local Chrome installation and direct the magent link in FF to be handled by Chrome - that sends the magnet link to the Unraid qbt. A bit using the scenic route, but it works.

Thanks for pointing this out, however when I tried that in Firefox the qbt client told me that my browser does not support this feature. Anyone any idea why and whether there is a possibility to circumvent this (other than using Chrome)?