7 minutes ago, 7hr08ik said:

Hey guys, need some help...

 

Updated the container today. It wont boot up anymore.

 

I run NordVPN, and everything has been running just fine for the past ... months/years...

Today I get the following...

 

2023-03-30 11:33:59.588541 [info] Host is running unRAID
2023-03-30 11:33:59.616601 [info] System information Linux 6c0837b709c6 5.19.17-Unraid #2 SMP PREEMPT_DYNAMIC Wed Nov 2 11:54:15 PDT 2022 x86_64 GNU/Linux
2023-03-30 11:33:59.648620 [info] OS_ARCH defined as 'x86-64'
2023-03-30 11:33:59.675093 [info] PUID defined as '99'
2023-03-30 11:33:59.708465 [info] PGID defined as '100'
2023-03-30 11:33:59.758393 [info] UMASK defined as '000'
2023-03-30 11:33:59.787916 [info] Permissions already set for '/config'
2023-03-30 11:33:59.817953 [info] Deleting files in /tmp (non recursive)...
2023-03-30 11:33:59.852272 [info] VPN_ENABLED defined as 'yes'
2023-03-30 11:33:59.879422 [info] VPN_CLIENT defined as 'openvpn'
2023-03-30 11:33:59.908262 [info] VPN_PROV defined as 'custom'
2023-03-30 11:33:59.944211 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/ch337.nordvpn.com.udp.ovpn
2023-03-30 11:33:59.994356 [warn] VPN confi
2023-03-30 11:33:59.994416                                              guration file /config/openvpn/*****.nordvpn.com.udp.ovpn remote port is missing or malformed, assuming port '1194'
2023-03-30 11:34:00.025007 [info] VPN remote server(s) defined as '***.***.***.**,'
2023-03-30 11:34:00.051578 [info] VPN remote port(s) defined as '1194,'
2023-03-30 11:34:00.077905 [info] VPN remote protcol(s) defined as 'udp,'
2023-03-30 11:34:00.107301 [crit] VPN_DEVICE_TYPE not found in /config/openvpn/*****.nordvpn.com.udp.ovpn, exiting...

** Press ANY KEY to close this window ** 

 

How can i add VPN_DEVICE_TYPE to the config?

 

I have tried re-downloading configs. I have tried multiple configs from Nord, and I always get the same response.

Deleted, and reinstalled the container. Tried with a clean appdata folder (renamed original and allowed it to recreate)

 

I have the same problem. i had to revert back to 4.5.2-1-01 which solved it for me 

Just now, gekoch said:

 

I have the same problem. i had to revert back to 4.5.2-1-01 which solved it for me 

Sorry to be a moron....but how do I revert back?

Figured it out

I also needed to downgrade due to similar error.

Same here with PIA VPN latest update break everythings with the same error has anyone else. revert back to 4.5.2-1-01 work's great

Experienced issues with Wireguard setup as well, after upgrading to latest version.

 

Specifically, the docker log stated:

vpn configuration file wg0.conf does not contain port on 'Endpoint' line

This even though the output goes on to dump the contents of wg0.conf, showing that the port is indeed defined.

 

Reverting to version 4.5.2-1-01 solved the issue.

investigated the issue, its due to a bug in the very recently released grep 3.10, looking at a workaround right now.

Same dealio here, applied the latest update now I'm getting the following when the container starts:

 

[warn] VPN configuration file /config/openvpn/openvpn.ovpn remote port is missing or malformed, assuming port '1194'

and

2023-03-30 07:51:22.980841 [crit] VPN_DEVICE_TYPE not found in /config/openvpn/openvpn.ovpn, exiting...

 

10 hours ago, LakersFan said:

Hey all,

I'm trying to run sabnzbd to run through qbittorrentvpn and referring to ques #25 of the VPN Docker FAQ:

Container to route through VPN

    Left click icon and 'Edit' container and toggle advanced view (top right).
    In 'Extra Parameters' enter --net=container:<vpn container name>.
    Go to 'Network Type' and select 'none'.
    Remove all ports defined (no ports required as we will be accessing it via the vpn container).
    Click on 'Apply'.

Container running VPN

    Left click icon and 'Edit' container and toggle advanced view (top right).
    Click on 'Add another Path, Port, Variable, Label or Device' and add in a 'config type' of 'port'.
    Enter in the applications Web UI port for 'container port' and any non conflicting port number for 'Host Port' (host port must not be used by another container).
    Edit 'VPN_INPUT_PORTS' env var and put applications Web UI port number in the 'value', if multiple ports required then use a comma to separate.
    Click on 'Apply'.

 

The issue I am unclear on is under "Container to route through VPN" it says to remove all ports defined. Then under "Container running VPN" it says to enter the applications Web UI port for 'container port' and any non conflicting port number for host port. However the default port of sab is 8080, which is the port that qbit uses. Can someone help clear this up? Also, which port would I add under 'VPN_INPUT_PORTS'?

 

 

In the QbittorrentVPN container (the container running the VPN):

Add the ports removed from the "container to route through VPN".

For example I use Flaresolverr and Jackett which use port 8191 and 9117 respectively. So I add under VPN_INPUT_PORTS 8191, 9171 (each removed ports separated by comma). Then I add a configuration (Add another Path, Port, ....) for config type Port, Name FlareSolverr (this is a description, any will do), container port 8191 (this comes from the port that was removed), host port 8192 (the new port that it should be using, I simply use original port+1) and that's it. Add another port for 9172 following the same nomenclature.

 

I think the way it works is, whatever the port from the container to route through VPN it has to go into the container running VPN and then out. So the original port goes into the container running the VPN and out as a new one for it to functions. 

 

In my case this is how it's working for my setup for all my containers routing through VPN. Lastly and you probably already know this, open the console on the container to route through VPN and do: curl ifconfig.io, this has to show the same IP address as the container running the VPN, it should be the end point that Qbiittorrent is connecting to. I use PIA, this is the same IP that I'm using as my end point. 

Edited March 30, 20233 yr by Rhodius

Anybody with the message '[crit] VPN_DEVICE_TYPE' showing up in the /config/supervisord.log file, please do a check for updates and apply the latest update.

1 hour ago, binhex said:

Anybody with the message '[crit] VPN_DEVICE_TYPE' showing up in the /config/supervisord.log file, please do a check for updates and apply the latest update.

Updated successfully and mine is now working again.  Thanks!

updated to the latest and I am not getting the VPN_DEVICE_TYPE error anymore

but I am getting "Bad compression stub (swap) decompression header byte: 250" 

Is this error connected to DNS? It seems like the DNS is working anymore. The links are all stalled, and trackers have problem updating. 

 

I went back to 4.5.2-1-01 and this version just works. 

Hello guys

 

It's been 2 weeks and i can't add any jackett rss feed into qbitorrent. its loads and load to nothing

 

I tried to flush the docker restar unraid  nothing works

 

If i copy the jackett rss to chrome the link show up

 

Example: http://10.0.0.22:9117/api/v2.0/indexers/gktorrent/results/torznab/api?apikey=fdvdvfdvfdvfdvfdvd&t=search&cat=&q=

 

Can someone help me

13 hours ago, Rhodius said:

In the QbittorrentVPN container (the container running the VPN):

Add the ports removed from the "container to route through VPN".

For example I use Flaresolverr and Jackett which use port 8191 and 9117 respectively. So I add under VPN_INPUT_PORTS 8191, 9171 (each removed ports separated by comma). Then I add a configuration (Add another Path, Port, ....) for config type Port, Name FlareSolverr (this is a description, any will do), container port 8191 (this comes from the port that was removed), host port 8192 (the new port that it should be using, I simply use original port+1) and that's it. Add another port for 9172 following the same nomenclature.

 

I think the way it works is, whatever the port from the container to route through VPN it has to go into the container running VPN and then out. So the original port goes into the container running the VPN and out as a new one for it to functions. 

 

In my case this is how it's working for my setup for all my containers routing through VPN. Lastly and you probably already know this, open the console on the container to route through VPN and do: curl ifconfig.io, this has to show the same IP address as the container running the VPN, it should be the end point that Qbiittorrent is connecting to. I use PIA, this is the same IP that I'm using as my end point. 

Thank you for responding. Unfortunately I believe my issue is qbittorrentvpn uses 8080 port as well as SABNZBD. In Sab, I removed ports 8080 and 8090. In qbittorrentvpn, I added 8080,8090 as VPN_INPUT_PORTS. I then added a new port, named it 'Sab Port', container 8080 and host 8085. (I left connection as TCP). In qbittorrentvpn already (not me adding), it has port 8080 already.

 

Qbit ports:

 

 

Qbit also has 8080 listed as a WEB_UI.

 

 

 

I tried playing around with the ports, but no success. Any idea?

 

 

 

Edited March 31, 20233 yr by LakersFan

I've been stuck on old version for a while now as it stopped working with recent updates.  Tried today with "latest" and still refuses to bring up web interface

 

binhex/arch-qbittorrentvpn:4.4.5-1-01  seems to be last working version for me (I'm using Privado not PIA like many here do).  It works but there's always that worry that you need latest versions

13 minutes ago, methanoid said:

I've been stuck on old version for a while now as it stopped working with recent updates.  Tried today with "latest" and still refuses to bring up web interface

 

binhex/arch-qbittorrentvpn:4.4.5-1-01  seems to be last working version for me (I'm using Privado not PIA like many here do).  It works but there's always that worry that you need latest versions

Attach the contents of supervisord.log to your next post. Be sure to redact users/passwords.

11 hours ago, francrouge said:

Hello guys

 

It's been 2 weeks and i can't add any jackett rss feed into qbitorrent. its loads and load to nothing

 

I tried to flush the docker restar unraid  nothing works

 

If i copy the jackett rss to chrome the link show up

 

Example: http://10.0.0.22:9117/api/v2.0/indexers/gktorrent/results/torznab/api?apikey=fdvdvfdvfdvfdvfdvd&t=search&cat=&q=

 

Can someone help me

Anyone has experience this ?

 

thx

7 hours ago, wgstarks said:

Attach the contents of supervisord.log to your next post. Be sure to redact users/passwords.

 

Thanks, attached. Should say its not running on unRAID as I mentioned weeks ago but same container obvs!

 

supervisord.log

I am trying to figure out how to get this running as a custom-app using truecharts on TrueNAS scale. I am getting this error and I’m not sure where to go from here. 
 

/usr/sbin/wg-quick: line 85: exec: sudo: not found

Hi 

 

I'm unable to add rss feed into qbitorrent.

 

I tried to delete everything and it's never working with jackett rss feed 

 

anyone can help

 

please

 

 

Edited April 1, 20233 yr by francrouge

On 3/30/2023 at 5:25 PM, kylaris said:

updated to the latest and I am not getting the VPN_DEVICE_TYPE error anymore

but I am getting "Bad compression stub (swap) decompression header byte: 250" 

Is this error connected to DNS? It seems like the DNS is working anymore. The links are all stalled, and trackers have problem updating. 

 

I went back to 4.5.2-1-01 and this version just works. 

 

I am getting this error also, and the container can't connect to the VPN/internet. 

I went to check on some downloads last night and was unable to access the webui from both the web browser and from the container in the Unraid UI. The container is listening on the proper port and functioning fine as I am able to send requests via Overseerr and they are downloading and importing into Plex without any issues. Anybody ever experienced this before? Seems really odd. I looked in the Unraid logs and nothing stands out or looks out of the ordinary. The container log itself is completely normal as well. I removed the container and image and reinstalled from the template and that did not solve the issue.

On 4/2/2023 at 3:45 PM, WalkerJ said:

 

I am getting this error also, and the container can't connect to the VPN/internet. 

edit your openvpn config file and remove any lines which contain 'comp-lzo' save the file and restart the container.

On 4/3/2023 at 12:18 PM, binhex said:

edit your openvpn config file and remove any lines which contain 'comp-lzo' save the file and restart the container.

 

There are no lines with 'comp-lzo' in the config file.

 

There is a line that says 'compress'. Is that related?

 

 
There are no lines with 'comp-lzo' in the config file.
 
There is a line that says 'compress'. Is that related?
 

Probably, try removing it

Sent from my 22021211RG using Tapatalk