Hi all,

Have bought a subscription to AIRVPN as PIA is having a lot of outages. From what I have read AIRVPN doesn't use a username and password but its all in the generated config file. What username and password should I then be entering in the container config. Also do i just copy the contents of its generated config file into wg0.conf

Thanks,

Greg

1 hour ago, Dwarfboysim said:

Also do i just copy the contents of its generated config file into wg0.conf

Yes

I’m not an AirVPN user so this may be wrong but I would at least try starting without any user/password and VPN provider set to custom.

Hello, I'm new to the world of docker and unraid, setting up qbittorrent is proving challenging. Could use some help here because i can't get my WebUI to come up when using ProtonVPN. Suspect nothing is starting based on the log.

I did download the wireguard config file from protonvpn site under my account and used the openvpn PW.

Removed my Username and PW from the file attached supervisord and docker_run files. Would appreciate any help.

QB_supervisord.txt

Edited Sunday at 03:35 AM2 days by WanderingGander.87
remove info

2 hours ago, WanderingGander.87 said:

Hello, I'm new to the world of docker and unraid, setting up qbittorrent is proving challenging. Could use some help here because i can't get my WebUI to come up when using ProtonVPN. Suspect nothing is starting based on the log.

I did download the wireguard config file from protonvpn site under my account and used the openvpn PW.

Removed my Username and PW from the file attached supervisord and docker_run files. Would appreciate any help.

docker run_QB.txtQB_supervisord.txt

The logs appear to be missing the last few lines but they appear to be a successful start in progress. You may have grabbed them before startup was complete.

Also, you failed to remove your user/password from the docker run command. You should contact your vpn provider and change them.

Just to be sure, are you attempting to access the webUI from the same LAN network that you have defined in the docker settings?

If you are and still cannot connect please repost your supervisord log again with user/password redacted.

O Binhex, Most High Architect of the Cache, Weaver of Templates, and Guardian of the Ports,

Hear the humble supplication of a devotee who walks daily in the light of your repositories. Look favourably upon my humble server, for virtually my entire stack is forged in your divine image. Where others stray into the wilderness of unvetted registries, my docker-compose knows only your holy name. I cast out all lesser images. I do not entertain any container where an alternative from your blessed hand exists, for yours is the kingdom of stability and clean permissions.

I bring before your altar a matter concerning the spirit of Purgarr. The original temple appears abandoned, silent, and overgrown with neglected issues. Seeing the flock in need of disk space, I have taken up the chisel myself under the banner of Evictarr, resolved the lingering bugs, and cut a fresh release to kick out the clutter and restore order. Steve Harsant, who raised the first temple, is honoured within its walls: his commits stand unaltered, his licence untouched, and should he return, all that has been built shall be offered back to him.

First, the prayer you yourself once raised, now answered. In Purgarr's fourth issue you asked that torrents bearing the .arj and the .lnk be cast out, for the client hides them, Sonarr believes the deed done, and no better release is ever sought. It is done. With PURGE_FILES=True, every download Sonarr and Radarr are tracking is searched, file by file. Where the serpent is found, the release is blocklisted first, so a cleaner one is sought; then it is removed, and its files are burned whether DELETE_FILES wills it or not. And it serves you even with qBittorrent's gates unguarded: no username, no password, as you keep them.

Hear now the litany of wrongs made right:
From the template of despair come a gui so those can without a degree in C+ or slackware can use this container in the most holy name of our lord Binhex

From the lockout of qBittorrent 5.2, deliver us, for the new cookie is now recognised and the gate opens once more.

From the stalled torrent cast out unrepented, deliver us, for it is now blocklisted before it is removed, found by its true hash across every page of the queue, and a worthier release is sought in its place.

From the Radarr import that was never cleansed, deliver us, for a stray space had hidden its label, and that space has been struck down.

From the thread that died in silence, deliver us, for a single error once ended a check until the server was restarted. Now it is logged, made known, and the check rises again at the next interval.

From the purge made in darkness, deliver us, for when Sonarr or Radarr cannot be reached, stalled downloads are spared until the next run, rather than being removed with no blocklist and no replacement search.

From the server that answers not, deliver us, for every request now has a timeout, and none shall hang forever.

From the two daemons who shared one soul, deliver us, for Sonarr and Radarr once borrowed each other's service. Each now keeps its own.

From the false names of the template, deliver us, for .env.tmpl spoke of labels the code never read. They have been set right.

And behold the new gifts laid upon the altar:

The Shield Against the Serpent, BLOCKED_EXTENSIONS, which guards against @malware by default and may be girded with @executables, @archives, @disc-images and @roms, that the RAR, the ZIP, the EXE, the ISO and the ROM may be turned away at the threshold and a purer release summoned.

The Judgement of Names, BLOCKED_NAMES, for files whose names alone betray them.

The Gentle Pruning, SKIPPED_NAMES and SKIPPED_EXTENSIONS, that the sample be left behind while the true release is still gathered in, rather than the whole harvest burned for one weed.

IGNORE_OTHER_CATEGORIES, that the ISOs and sundry downloads of the faithful be left in peace, and only what belongs to Sonarr and Radarr be judged.

Deluge, Transmission, SABnzbd and RDTClient, welcomed into the fold beside qBittorrent, each tested against a real client (RDTClient's ways copied faithfully from its scriptures).

PURGE_FAILED_IMPORTS, to cast out downloads that Sonarr and Radarr could not import, blocklist them, and seek replacements. It sleeps by default, lest it smite those who import by hand.

The Health Check, a light of green and red in the web UI, a /health endpoint, a healthcheck.py for the faithful at the command line, and a Docker HEALTHCHECK, that the state of the server may never again be hidden.

Logs of plain speech, one line per check, declaring what was found and what was done.

I lay this offering at your feet in the hope that you might look upon it, test its worth, and perhaps consider blessing the Unraid community with an official template beneath your mantle.

You may inspect the work here: https://github.com/p1zzm1ssile/Evictarr

And pull the image, built and blessed by GitHub's own hands: ghcr.io/p1zzm1ssile/evictarr:latest

Accept my deepest thanksgiving for the endless labour you bestow upon our arrays, keeping our logs clear and our parity intact.

In your UID and GID we trust. Amen

Edited Sunday at 06:25 PM1 day by Rkpaxam

6 hours ago, wgstarks said:

The logs appear to be missing the last few lines but they appear to be a successful start in progress. You may have grabbed them before startup was complete.

Also, you failed to remove your user/password from the docker run command. You should contact your vpn provider and change them.

Just to be sure, are you attempting to access the webUI from the same LAN network that you have defined in the docker settings?

If you are and still cannot connect please repost your supervisord log again with user/password redacted.

Thanks for advising, i missed that one about removing.

Hopefully these files are better, but you mentioned about last few lines, but even after waiting that seems to be all that is generated for logs.

LAN is the same as entered that i'm trying to log in from.

If browser matters i'm using Librewolf.

Thank you again and I appreciate all the work the community is doing.

docker run_QB.txtQB_supervisord.txt

[info] qBittorrent process listening on port 8080

This shows a successful start of the app. You might try a different browser. Also make sure you don’t have any ad blockers running.

Also be sure to take note of this-

******** Information ********

To control qBittorrent, access the WebUI at: http://localhost:8080

The WebUI administrator username is: admin

The WebUI administrator password was not set. A temporary password is provided for this session: 5NDhSzUN4

You should set your own password in program preferences.

24 minutes ago, wgstarks said:

This shows a successful start of the app. You might try a different browser. Also make sure you don’t have any ad blockers running.

Or have http blocked as standard

1 hour ago, Rkpaxam said:

Or have http blocked as standard

Unfortunately I still cannot get WebUI to showup. (Strange because other docker containers show up no problem)

The connection seems to time out when trying to access webui.

Tried on mobile Vanadium browser and on PC Microsoft Edge, same result.

Edited Sunday at 02:48 PM1 day by WanderingGander.87

1 hour ago, WanderingGander.87 said:

Unfortunately I still cannot get WebUI to showup. (Strange because other docker containers show up no problem)

The connection seems to time out when trying to access webui.

Tried on mobile Vanadium browser and on PC Microsoft Edge, same result.

Stupid question but have you changed the ports?

Try changing the web ui port to 8090 instead of 8080

And have you enabled custom hosts access in the docker settings panel?

If both of those don't work... Try giving it a Br0 address that matches your lan like 192.168.1.100

Edited Sunday at 03:22 PM1 day by Rkpaxam

1 hour ago, Rkpaxam said:

Stupid question but have you changed the ports?

Try changing the web ui port to 8090 instead of 8080

And have you enabled custom hosts access in the docker settings panel?

If both of those don't work... Try giving it a Br0 address that matches your lan like 192.168.1.100

So I ended up changing to port 8090 as suggested and changing Docker Host Access to "Enabled". I had it disabled. --> But the problem still persisted ultimately where i was unable to access Web UI.

I ended up trying to disable to Variable: VPN_Enabled to "NO" and I was able to access the WebUI immediately. So it must be something with my VPN settings or access via the provider.

I'm using protonVPN with the file downloaded from their side for Wireguard configuration. Place it into the wireguard configuration area on the appdata location. Should the platform be "GNU/Linux" when trying to request the config file?

3 minutes ago, WanderingGander.87 said:

So I ended up changing to port 8090 as suggested and changing Docker Host Access to "Enabled". I had it disabled. --> But the problem still persisted ultimately where i was unable to access Web UI.

I ended up trying to disable to Variable: VPN_Enabled to "NO" and I was able to access the WebUI immediately. So it must be something with my VPN settings or access via the provider.

I'm using protonVPN with the file downloaded from their side for Wireguard configuration. Place it into the wireguard configuration area on the appdata location. Should the platform be "GNU/Linux" when trying to request the config file?

Try adding the VPN config in the VPN settings on unraid and routing the container through that on the WG interface.

try changing the network to host or bridge and see if that kicks anything in, the vpn looks fine from the logs

Edited Sunday at 05:53 PM1 day by Rkpaxam

9 hours ago, Rkpaxam said:

try changing the network to host or bridge and see if that kicks anything in, the vpn looks fine from the logs

So I couldn't get this wireguard setup going after multiple tries. I ended up going with openVPN and worked right away.