33 minutes ago, TexasUnraid said:

I am on qbittorrent 4.3 and radarr 0.2.0.1504. Imports work perfectly. Nzbget on the other hand takes forever to import.

 

Is there a way to update to radarr v3? I am running the binhex container, I already updated to the V3 sonarr and it is much nicer but heard radarr is not ready yet?

It's ready AFAIK, even people on reddit say that even though its not official that for the most part, barring some edge case weirdness of your particular setup that its good to go  for at least a while now.

Backup your whole persistent data for radarr dir:

tar -zcvf radarr.gz /yourpathto/radarr/

 

then in my case, in my docker-compose, i simply change the image it pulls

    image: linuxserver/radarr:nightly

 

Badda-bing, badda-boom, that's it.

 

Worst comes to worst, you blow up the persistent data directory, because some of it will be updated to v3 versions, and untar the 0.2 copy and roll back to 0.2.

 

 

I'm surprised it works in 0.2 though, it had been broken AF for me, maybe someone backported the fix *shrug*

 

Edited November 16, 20205 yr by mooky

so my privoxy wasnt booting, i deleted the privoxy folder in docker/config    now its working

I had something of a network issue due to accidentally colliding my comp's IP with my UnRAID server's IP and at the same time I had to switch from using OpenVPN via my VPN to using Wireguard, so I'm not 100% on which action is causing me problems here...

 

Basically, I can't get Wireguard to connect. Log is attached

binhexlog.txt

11 minutes ago, queen-adreena said:

I had something of a network issue due to accidentally colliding my comp's IP with my UnRAID server's IP and at the same time I had to switch from using OpenVPN via my VPN to using Wireguard, so I'm not 100% on which action is causing me problems here...

 

Basically, I can't get Wireguard to connect. Log is attached

binhexlog.txt 24.55 kB · 2 downloads

Not sure if this is the cause but I see you have changed the name servers to google. You might try switching them back to the default.

Just now, wgstarks said:

Not sure if this is the cause but I see you have changed the name servers to google. You might try switching them back to the default.

What is the default? You mean the ones in my binhex config panel?

2 minutes ago, queen-adreena said:

What is the default? You mean the ones in my binhex config panel?

209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

17 minutes ago, wgstarks said:

209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

Thanks for the quick response, but unfortunately, I'm still getting the exact same error, so I don't think it was connected to that.

29 minutes ago, queen-adreena said:

Thanks for the quick response, but unfortunately, I'm still getting the exact same error, so I don't think it was connected to that.

Your logs are showing a name resolution error. Was worth a shot.

Still can't find the answer to this one. Crux of the error is:

2020-11-18 19:06:51,914 DEBG 'start-script' stderr output:
Unable to parse IP address: `'
Configuration parsing error

2020-11-18 19:06:51,916 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0

2020-11-18 19:06:51,962 DEBG 'start-script' stdout output:
[warn] WireGuard interface failed to come 'up', exit code is '1'

Full log is attached in an above post.

Where do I find the default username and password?

This is probably something obvious that i completely missed, I searched for 'user' in

https://github.com/binhex/documentation/blob/master/docker/faq/general.md

https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

 

1 minute ago, veelckoo said:

Where do I find the default username and password?

This is probably something obvious that i completely missed, I searched for 'user' in

https://github.com/binhex/documentation/blob/master/docker/faq/general.md

https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

 

The openVPN portion doesn't have any defaults, you need to have an already paid-for VPN service you subscribe to.

 

The default login/password for qbittorrent however is:

login: admin

password: adminadmin

 

Change that the first chance you get.

Thank you for reply.

Sorry for not being clear enough - I am looking for qBittorrent Web UI credentials.

Tried admin/adminadmin but that does work.
Looked into qBittorrent.conf but that does not show any credentials

[AutoRun]
enabled=false
program=

[Preferences]
Connection\PortRangeMin=6881
Connection\UPnP=false
General\Locale=en
General\UseRandomPort=false
Queueing\QueueingEnabled=false
WebUI\Address=*
WebUI\CSRFProtection=false
WebUI\LocalHostAuth=false
WebUI\Port=8080
WebUI\ServerDomains=*
WebUI\UseUPnP=false

 

Are you able to bring up the webUI ?  If so, the default is as I stated.

There are 2 settings in the conf file:

WebUI\Password_PBKDF2=<HASHED PASSWORD HERE>
WebUI\Username=mooky

But those are added once you log in through the GUI, and go into options to change it.

 

What did you define as your WEBUI_PORT?

 

Here's my docker-compose yaml file that fires my instance of the docker:

services:
  qbittorrentvpn:
    image: binhex/arch-qbittorrentvpn
    container_name: qbitvpn
    volumes:
      - /mnt/myfiles:/data
      - /persiststorage/qbitvpn:/config
    environment:
      - PUID=99
      - PGID=100
      - TZ=America/Chicago
      - VPN_ENABLED=yes
      - VPN_USER=p1234567  # change as necessay
      - VPN_PASS=9dfglkj43G$3 #change as necessary
      - VPN_PROV=pia  #change as necessary
      - VPN_CLIENT=openvpn
      - STRICT_PORT_FORWARD=no
      - ENABLE_PRIVOXY=yes
      - LAN_NETWORK=192.168.1.0/24
      - WEBUI_PORT=29501
      - UMASK=000
    cap_add:
      - NET_ADMIN
    ports:
      - "29500:6881"
      - "29500:6881/udp"
      - "29501:29501"
      - "8118:8118"
    restart: unless-stopped

 

Edited November 18, 20205 yr by mooky
werds are hard, must edit....

I was able to use the credentials you provided after I restarted the the Docker engine. I have no idea why it wasn't accepting those befor (tried typing, copy-paste) did not work.

Now to play with VPN and qbittorrent.

Thank you for your help!

I have been using this container along with SWAG from linuxserver.io on my trusty Ubuntu 18.04.5 standalone server for at least a year if not longer.

I dont remember the last time i touched the server much less updated it...its been working great, out of no where the webgui stopped working i get this error 

 

502 Bad Gateway
nginx/1.18.0

 

My logs mentioned

 

modprob: FATAL: Module iptable_mangle not found in directory /lib/modules/5.4.0-54-generic
 

so then i used

 

sudo /sbin/modprobe iptable_mangle

 

and that got resolved but now its complaining about not loading the tun mod

 

modprobe: FATAL: Module tun not found in directory /lib/modules/5.4.0-54-generic
 

How do i fix this?

 

Things i have tried to fix the problem

upgraded to 20.04

sudo chown -R 777 /entire container directory

made sure the UID and GID in the docker compose file match the user issuing the docker-compose command

 

EDIT

I just found this

https://www.kernel.org/doc/Documentation/networking/tuntap.txt

I'm gonna read it and see what I find

 

 

Thanks in Advance

 

 

 

Edited November 20, 20205 yr by Cytomax

Hi i'm not able to enter the default user and password

 

I tried admin adminadmin.

 

I tried to manually add my info its not working 

 

Anyone has an idea ?

On 11/20/2020 at 2:05 AM, Cytomax said:

I have been using this container along with SWAG from linuxserver.io on my trusty Ubuntu 18.04.5 standalone server for at least a year if not longer.

I dont remember the last time i touched the server much less updated it...its been working great, out of no where the webgui stopped working i get this error 

 

502 Bad Gateway
nginx/1.18.0

 

My logs mentioned

 

modprob: FATAL: Module iptable_mangle not found in directory /lib/modules/5.4.0-54-generic
 

so then i used

 

sudo /sbin/modprobe iptable_mangle

 

and that got resolved but now its complaining about not loading the tun mod

 

modprobe: FATAL: Module tun not found in directory /lib/modules/5.4.0-54-generic
 

How do i fix this?

 

Things i have tried to fix the problem

upgraded to 20.04

sudo chown -R 777 /entire container directory

made sure the UID and GID in the docker compose file match the user issuing the docker-compose command

 

EDIT

I just found this

https://www.kernel.org/doc/Documentation/networking/tuntap.txt

I'm gonna read it and see what I find

 

 

Thanks in Advance

 

 

 

ROFL.. well i feel dumb... looks like qbitorrent wasnt starting because the bahamas.ovpn file wasnt working.. i changed to a different .ovpn file and everything loaded up.... oh well i learned a lot about modules

23 hours ago, francrouge said:

Hi i'm not able to enter the default user and password

 

I tried admin adminadmin.

 

I tried to manually add my info its not working 

 

Anyone has an idea ?

Same thing happened to me... i just deleted the whole container and started over again... unless someone has a better idea

1 hour ago, Cytomax said:

Same thing happened to me... i just deleted the whole container and started over again... unless someone has a better idea

I just found out it was some autorisation in google chrome since default password was working in internet explorer.

 

 

I recently updated the container and I can no longer access the WebUI when VPN is active. Disabling VPN restores access. Any ideas on what might have changed? I've tried resetting WebUI ports but that hasn't helped any.

7 minutes ago, eetsumrobins said:

I recently updated the container and I can no longer access the WebUI when VPN is active. Disabling VPN restores access. Any ideas on what might have changed? I've tried resetting WebUI ports but that hasn't helped any.

Attach the supervisord log to your next post.

Attached is the master log as well as a copied log just containing info immediately after the launch of the container

 

Edited November 26, 20205 yr by eetsumrobins

9 hours ago, eetsumrobins said:

 

Attached is the master log as well as a copied log just containing info immediately after the launch of the container

 

Not sure who your vpn provider is but you should change your user name/password since it’s posted in the logs.

11 hours ago, eetsumrobins said:

Attached is the master log as well as a copied log just containing info immediately after the launch of the container

supervisord.log 1.16 MB · 1 download supervisord_clean_launch.txt 19.39 kB · 1 download

is this correctly defined, from your log:-

2020-11-25 23:17:31.333918 [info] LAN_NETWORK defined as '192.168.1.0/24'

if you are unsure see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Damn it, completely missed that line. Corrected and things are working properly now. Thanks for the help!