docker and portainer ip question

So you can mark the thread as resolved?

Forget about mentions of 172.x IP addresses. Those belong to the container. Your VPN IP remote address is: 107.173.59.99

This docker images has unusual properties (compared to almost all others) with respect to port assignments. It also has an incorrect WEBUI environment variable specification.

You can absolutely NOT use a port spec that has a different host side and container side port. It will not work.

INCORRECT example: 8081:8080

Edit:

CORRECT example: 8080:00

CORRECT example: 8080:8080

This environment variable is INCORRECT even though the documentation shows it this way: WEBUI_PORT_ENV=8081

This is a sample of the correct environment variable and I provided it to you this way in my stack: WEBUI_PORT=8080 Use of this variable may or may not be optional. I say it's not option, use it because the documentation is at least partially incorrect.

Any selection you make as your choice for the above discussed port must be identical in all three places where it is used.

I do not have any ports open on my router and forwarded to my omv machine. In my use case with my VPN provider (Torguard.net) this is unnecessary. Once you have a working setup you may want to try disabling your port forwards as a test.

Quote from HackitZ

is there an environment variable i can add for the monitored folder?

I've tried adding

/srv/dev-disk-by-uuid-c02f9840-5c78-47e3-9277-345213d858b3/TorrentZ_Uploads

and

/TorrentZ_Uploads

in the qbittorent settings but it's not working.

Display More

You can not use host side paths like /srv/dev/.... anywhere inside the qbittorrent GUI. All paths there must be relative to the container, not the host.

For a user chosen monitored folder, create a new subdirectory on your host like this:

/srv/dev-disk-by-uuid-c02f9840-5c78-47e3-9277-345213d858b3/TorrentZ/monitored

Then in the qbittorrent GUI set:

Automatically add torrents from: /downloads/monitored

Override Save Location: Default Save Location

As with all folder location you use with any docke make sure that the PUID the container runs as has the correct permissions it needs to work with the folders.

Quote from HackitZ

should this work?

/srv/dev-disk-by-uuid-c02f9840-5c78-47e3-9277-345213d858b3/TorrentZ_Uploads

I added this in qbittorrent GUI:

Automatically add torrents from: /downloads/TorrentZ_Uploads then selected monitired folder in the drop down.

Most likely would not work.

The container will only talk to a host filesystem directory identified via a volume bind mount and only through the container directory bound to that host side directory. I don't see this in what you show.

Is there some reason you can't use what's already available that already works for this?

With some images you can actually make up undocumented stuff so long as it strictly follows the conventions of what it would expect. You could always try and see. But this image is touchy all by itself anyway.

Not sure what to expect with feature requests on this one. It has reported problems that have still not been fixed.

Read this a bit on the diagonal, but just some thoughts on 2 points (this is on linuxserver/docker-qbittorrent so it works on mcnugem's) :

1. The WebUI port can be change to whatever you want, if you use the YML/stack with, for eg:

- WEBUI_PORT_ENV=40000 #the port number you want to access the WebGUI
....
ports:
- xxxx:40000 # xxxx the port you want to expose on the Host : The port selected for WEBUI

2. qBittorrent has a folder to "watch" for torrents (bind a volume/folder to it) :

- /srv/dev-disk-xxxxxx/the folder were your torrent files will be:/watch

Then, on the WebUI "Options-->Downloads", set the downloads to automatic and set the folder to "watch"

Quote from Soma

Read this a bit on the diagonal, but just some thoughts on 2 points (this is on linuxserver/docker-qbittorrent so it works on mcnugem's) :

1. The WebUI port can be change to whatever you want, if you use the YML/stack with, for eg:

Code

- WEBUI_PORT_ENV=40000 #the port number you want to access the WebGUI
....
ports:
- xxxx:40000 # xxxx the port you want to expose on the Host : The port selected for WEBUI

Please see this:

https://github.com/MarkusMcNug…-qBittorrentvpn/issues/97

As for the watch folder, your suggestion is worth a try. I use it the way it already is because I had no need to change it.

Display More

It seems that the environment is not correct, according to the first 2 replies:

Instead of WEBUI_PORT_ENV=xxxxxx (this is what was stated in the readme for mcnugem), it should be only WEBUI_PORT=xxxxx (as stated on the linuxserver readme)

As for the "watch" folder, I don't use it (I add the torrents via the WebGui, after downloading them to my PC).

Only showed how it's supposed to be, according to the documentation,

I trust it works,