[[Support] binhex - qBittorrentVPN]

Figured out magnet links via the web ui, so posting if it might help others utilizing the forum search. They are tricky, even more so if you are using chrome (on Win 10, probably 11 too).

Magnet requires QBT running the web ui in HTTPS. To do this we need a self signed cert.
Pop open a console for this docker container, then make a new directory with `mkdir /config/qBittorrent/config/ssl` and enter it with `cd /config/qBittorrent/config/ssl`. Create a new self signed key with `openssl req -new -x509 -nodes -out server.crt -keyout server.key`. Enter whatever you want when it prompts; don't enter empty strings.

Next, fix the damn folder perms! `chown -R nobody:user /config/qBittorrent/config/ssl`. Otherwise the files/folder are owned by root:root and QBT will error later on. Enter the container, Option -> Web UI, then:

 

1. Check "Use HTTPS instead of HTTP"
2. For Certificate, enter: /config/qBittorrent/config/ssl/server.crt
3. For Key, enter: /config/qBittorrent/config/ssl/server.key

Restart the container, and use the HTTPS in the url. The browser might complain about an 'unsafe' website, click advanced and proceed anyway. If you see the UI, all is good.

Next we have to associate the magenet link. In the web ui, click Tools -> Register to handle magnet links. The browser should prompt something, accept it. If you're running firefox, that should be it - you can click a mag torrent link and it should work (there might be another browser prompt). I recommend you ctrl+click the mag link, so it opens it in another tab. If you're using chrome however... you will need to do the below.

https://github.com/qbittorrent/qBittorrent/issues/12605#issuecomment-1385058678

Quote

 

Like jzyinq said above, Firefox works just fine as of this posting. The issue is Chrome - but I have a work around for Windows. Using an old qbt v4.4.2, but I think this solution will work for the newer version as well.

 

Chrome is expecting the Windows OS system registry to have an entry for the magnet link, and when it doesn't find one, it fails out.

 

Run this registry script - be sure to modify the IP and port if needed (or replace them with a url).

 

;Associate magnet files with qBittorrent webui
[HKEY_CLASSES_ROOT\magnet]
@="URL:magnet Protocol"
"URL Protocol"=""
[HKEY_CLASSES_ROOT\magnet\shell]
[HKEY_CLASSES_ROOT\magnet\shell\open]
[HKEY_CLASSES_ROOT\magnet\shell\open\command]
@="\"C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\" \"https://127.0.0.1:8080/#download=%1\""

 

After adding the above to your registry, navigate to chrome://settings/handlers and remove any existing entries for 'magnet'.

In the qBittorrent web UI, Tools -> Register to handle magnet links. And that's it! Magnet links should now work. 🙌

 

*Note*: This does not break Firefox functionality - ff magnets will still open in ff.

 

 

 

I'm assuming there is a similar work around on on mac/linux if you are using chrome. Annoying this doesn't work eaiser, and there is this much work involved. Hope this helps!

[VM Fails to start VNC (QXL)]

Sorry for the necro - I was having the same issue and this was the 2nd link off google.

I had the opposite fix compared to lurkio, issue presented on Chrome, switching to Firefox did the trick.

[New Payment Options]

Yeah, was looking for what ^ said, "none of the above," consider me a control group. Really I only care for credit/debit card, I see extra options as unnecessary.

[[SUPPORT] - Portainer-CE]

Have issues trying to build a new image from a dockerfile.

From Images -> Build a new image, I'm trying to run a `COPY /df/ffp-n8n/docker-entrypoint.sh /docker-entrypoint.sh`.

In the unraid docker template, I have a path mapping for `/df -> /mnt/user/appdata/docker/`.

Lastly, the file in unraid exists at `/mnt/user/appdata/docker/ffp-n8n/docker-entrypoint.sh`.

 

However I get an error: `COPY failed: file not found in build context or excluded by .dockerignore: stat df/ffp-n8n/docker-entrypoint.sh: file does not exist`

When I attempt to check the path via the dropdown -> Console UI, I get an error `OCI runtime exec failed: exec failed: container_linux.go:367: starting container process caused: exec: "sh": executable file not found in $PATH: unknown`

Any help would be greatly appreciated!

[[Support] FoxxMD - pinry]

@GooseGoose I had the exact same error as you. Please see here: https://docs.getpinry.com/passwords/ (read the note at the bottom). If you use the Unraid docker console, then you want to run

python manage.py createsuperuser --settings=pinry.settings.docker

 

The official Pinry docs are also super vague on this. Seems very odd that default credentials do not exist... Really it seems like Pinry is a pita to use so far...

[Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array]

I'm trying to run a Mango docker instance with my Windows 10 SMB share. Im getting an error: `[INFO] Starting DB optimization
Unhandled exception: database is locked (SQLite3::Exception)`

 

The docker mount setting is `/mnt/disks/MYDISK/`. I can terminal from Unraid and read/write to the folder without issue. From my google searches, this could be an issue with how the docker talks to the SMB share; possibly something to do with "byte range lock requests"? I've tried setting "Access Mode" in the docker configuration (both R/W Slave and R/W Share).

This docker does work if I don't use the SMB share, but I'd really like to use it since the SMB share holds 50x the capacity of my Tower. Any ideas how I can get this to work?