[Support] MarkusMcNugens Docker Repository


Recommended Posts

Hey, So I am running into an odd issue. I have the docker setup and I have changed the WEBUI ports to 6010 and changed it in the config file and the lan network to 192.168.0.0/24. When I try to connect to the webui it fails, if I turn the vpn off and try it works fine. Any thoughts?

 

2018-12-30 19:54:15.085103 [info] VPN_ENABLED defined as 'yes'
2018-12-30 19:54:15.108729 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/US_Las_Vegas.ovpn
dos2unix: converting file /config/openvpn/US_Las_Vegas.ovpn to Unix format...
2018-12-30 19:54:15.139019 [info] VPN remote line defined as 'us-lasvegas.privateinternetaccess.com 1198'
2018-12-30 19:54:15.159417 [info] VPN_REMOTE defined as 'us-lasvegas.privateinternetaccess.com'
2018-12-30 19:54:15.179087 [info] VPN_PORT defined as '1198'
2018-12-30 19:54:15.199322 [info] VPN_PROTOCOL defined as 'udp'
2018-12-30 19:54:15.218725 [info] VPN_DEVICE_TYPE defined as 'tun0'
2018-12-30 19:54:15.237422 [info] LAN_NETWORK defined as '192.168.0.0/24'
2018-12-30 19:54:15.257325 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
2018-12-30 19:54:15.276949 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2018-12-30 19:54:15.298100 [info] Adding 8.8.8.8 to resolv.conf
2018-12-30 19:54:15.316610 [info] Adding 8.8.4.4 to resolv.conf
2018-12-30 19:54:15.334796 [info] Starting OpenVPN...
Sun Dec 30 19:54:15 2018 WARNING: file 'credentials.conf' is group or others accessible
Sun Dec 30 19:54:15 2018 OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 5 2018
Sun Dec 30 19:54:15 2018 library versions: OpenSSL 1.1.0g 2 Nov 2017, LZO 2.08
Sun Dec 30 19:54:15 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]199.127.56.115:1198
Sun Dec 30 19:54:15 2018 UDP link local: (not bound)
Sun Dec 30 19:54:15 2018 UDP link remote: [AF_INET]199.127.56.115:1198
Sun Dec 30 19:54:15 2018 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sun Dec 30 19:54:18 2018 [d2c3cc3a096826d7413d1c3a2cf62c6f] Peer Connection Initiated with [AF_INET]199.127.56.115:1198
Sun Dec 30 19:54:19 2018 TUN/TAP device tun0 opened
Sun Dec 30 19:54:19 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Sun Dec 30 19:54:19 2018 /sbin/ip link set dev tun0 up mtu 1500
Sun Dec 30 19:54:19 2018 /sbin/ip addr add dev tun0 local 10.6.10.6 peer 10.6.10.5
Sun Dec 30 19:54:19 2018 Initialization Sequence Completed
2018-12-30 19:54:19.366890 [info] WebUI port defined as 6010
2018-12-30 19:54:19.387864 [info] Adding 192.168.0.0/24 as route via docker eth0
RTNETLINK answers: File exists
2018-12-30 19:54:19.407133 [info] ip route defined as follows...
--------------------
0.0.0.0/1 via 10.6.10.5 dev tun0
default via 192.168.0.1 dev eth0
10.6.10.1 via 10.6.10.5 dev tun0
10.6.10.5 dev tun0 proto kernel scope link src 10.6.10.6
128.0.0.0/1 via 10.6.10.5 dev tun0
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.152
199.127.56.115 via 192.168.0.1 dev eth0
--------------------
iptable_mangle 16384 2
ip_tables 24576 5 iptable_filter,iptable_nat,iptable_mangle
2018-12-30 19:54:19.429013 [info] iptable_mangle support detected, adding fwmark for tables
2018-12-30 19:54:19.460735 [info] Docker network defined as 192.168.0.0/24
2018-12-30 19:54:19.500971 [info] Incoming connections port defined as 8999
2018-12-30 19:54:19.522651 [info] iptables defined as follows...
--------------------
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -d 192.168.0.0/24 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 6010 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 6010 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 8999 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 192.168.0.0/24 -d 192.168.0.0/24 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 6010 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 6010 -j ACCEPT
-A OUTPUT -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 8999 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
--------------------
Adding 100 group
groupadd: GID '100' already exists
Adding 99 user
useradd: UID 99 is not unique
2018-12-30 19:54:19.560569 [info] UMASK defined as '002'
2018-12-30 19:54:19.583026 [info] Starting qBittorrent daemon...
Logging to /config/qBittorrent/data/logs/qbittorrent-daemon.log.
2018-12-30 19:54:20.609145 [info] qBittorrent PID: 209
2018-12-30 19:54:20.610596 [info] Started qBittorrent daemon successfully...

Link to comment

Hi @MarkusMcNugen

 

I don't suppose you'd be able to help with this issue I'm facing with your OpenConnect/ocserv image?

 

Any and every connection I have disconnects after 240 seconds (which, coincidentally, is the auth-timeout period). I've tried connecting to my VPN server via OpenConnect on Android and via CLI on a Ubuntu machine but they both disconnect after 240 seconds and then reconnect all over again.

 

To rule out any errant config issues on my part, I tried setting up a "clean/default config" version of your image without any changes to the ocserv.conf file (i.e literally just running this:)

docker run --privileged  -d -p 4443:4443 -p 4443:4443/udp markusmcnugen/openconnect

And yet despite this, my client devices will still disconnect after 240 seconds only to reconnect all over again.

 

On my Ubuntu box, this is the output when the 240 seconds lapse:

.....stuff beforehand elided for brevity
DTLS option X-DTLS-Content-Encoding : oc-lz4
DTLS initialised. DPD 90, Keepalive 32400
Connected as 192.168.1.182, using SSL + lz4
Established DTLS connection (using GnuTLS). Ciphersuite (DTLS1.2)-(PSK)-(AES-256-GCM).
DTLS connection compression using LZ4.
Initiating IPv4 MTU detection (min=717, max=1434)
No change in MTU after detection (was 1434)
Connect Banner:
| Welcome to {{$SERVER_NAME}}

Error: Invalid prefix for given prefix length.
SSL read error: The TLS connection was non-properly terminated.; reconnecting.
SSL negotiation with mydomain.tld
Server certificate verify failed: signer not found
Connected to HTTPS on mydomain.tld
TCP_INFO rcv mss 1428, snd mss 1448, adv mss 1448, pmtu 1500
Got CONNECT response: HTTP/1.1 200 CONNECTED

 

In particular, it's the line that says "SSL read error: The TLS connection was non-properly terminated.; reconnecting." which seems to be causing all of this I think?

 

Any thoughts would be appreciated.

 

And of course, happy new year :)

Link to comment

Trying to get the SFTP docker working but I'm having some trouble. I've read the github page but it isn't exactly clear.

 

So far I have created the users.conf file and added a single user as mentioned on the github page. The container now starts, but I am unsure whether or not I am supposed to run it in 'host' or 'bridge' or something else. It's just running on port 22. As follows:

 

kha6twBM.png

 

 

I haven't set a directory yet to share, but I want to share the main storage directory. In this case it's "/tank"

 

The problem is, that I cannot even log in yet with Filezilla on my Windows PC. The connection just keeps timing out. I don't understand why.

 

Can I get some help?

Edited by plantsandbinary
Link to comment

Hi MarkusMcNugens,

 

I've installed the sftp docker, configured users with users.conf, and added user keys. I can see that the docker created the users appropriately and copied the user keys to their respective authorized_keys files as well as copied the userkey files to their respective folders correctly. The problem I'm having is that when I connect to the SFTP server, I'm able to log in without using my userkey in my client (only the password is required). I've restarted the docker, but the issue persists. 

Link to comment
  • 3 weeks later...
On 1/5/2019 at 5:18 PM, plantsandbinary said:

Trying to get the SFTP docker working but I'm having some trouble. I've read the github page but it isn't exactly clear.

 

So far I have created the users.conf file and added a single user as mentioned on the github page. The container now starts, but I am unsure whether or not I am supposed to run it in 'host' or 'bridge' or something else. It's just running on port 22. As follows:

 

kha6twBM.png

 

 

I haven't set a directory yet to share, but I want to share the main storage directory. In this case it's "/tank"

 

The problem is, that I cannot even log in yet with Filezilla on my Windows PC. The connection just keeps timing out. I don't understand why.

 

Can I get some help?

I'm having the same problem.

 

1242560935_ScreenShot2019-01-28at3_45_19PM.thumb.png.178a423f049555b45e5616a58ce22a62.png

 

I think I've created the home directory.

 

 

This is my users.conf:

#user:pass:1001:100
hdhr:hdhr:1002:100

Here is my output:

MacBook-Pro:~ dga$ sftp [email protected]:2222
[email protected]: Permission denied (publickey,keyboard-interactive).
Connection closed
MacBook-Pro:~ dga$ 

The unRAID ssh server is configured to only use a key and no passwords. Could those settings be affecting the docker? What additional configuration is needed?

 

Thanks,

David

 

 

docker log:


Mon Jan 28 23:25:04 America 2019 [info] Existing jail.conf found. Copying to container filesystem!
Mon Jan 28 23:25:04 America 2019 [info] Existing sshd_config found. Copying to container filesystem!
Creating users...
[entrypoint] Parsing user data: "hdhr:hdhr:1002:100"
* Starting system logging syslog-ng
...done.
[entrypoint] Executing sshd
* Starting OpenBSD Secure Shell server sshd
...done.
[entrypoint] Executing fail2ban
* Starting authentication failure monitor fail2ban
...done.
Jan 28 23:25:05 c682e4b023fa sshd[71]: Server listening on 0.0.0.0 port 22.

Jan 28 23:25:05 c682e4b023fa sshd[71]: Server listening on :: port 22.

Mon Jan 28 23:29:44 America 2019 [info] Existing jail.conf found. Copying to container filesystem!
Mon Jan 28 23:29:44 America 2019 [info] Existing sshd_config found. Copying to container filesystem!
* Starting system logging syslog-ng
...done.
[entrypoint] Executing sshd
* Starting OpenBSD Secure Shell server sshd
...done.
[entrypoint] Executing fail2ban
* Starting authentication failure monitor fail2ban
...done.
Jan 28 23:29:44 c682e4b023fa sshd[51]: Server listening on 0.0.0.0 port 22.

Jan 28 23:29:44 c682e4b023fa sshd[51]: Server listening on :: port 22.

 

Link to comment

Hi Markus!

 

SFTP is creating the users in the container from the users.conf file on the first run, but it does not appear to handle when users are added to the file and the docker is restarted. Is it possible to have the container add additional users that may be added to the users.conf file after the first run? It would also be pretty sweet if the startup script could also update the user passwords using the users.conf file on startup, making it possible to manage users without using the containers shell.

  • Upvote 1
Link to comment

I get the following error with SFTP:

Feb 5 21:10:04 b449918f5a15 sshd[53]: Server listening on 0.0.0.0 port 22.
Feb 5 21:10:04 b449918f5a15 sshd[53]: Server listening on :: port 22.
Feb 5 21:16:13 b449918f5a15 sshd[85]: Invalid user user from 10.24.0.30
Feb 5 21:16:13 b449918f5a15 sshd[85]: input_userauth_request: invalid user user [preauth]
Feb 5 21:16:13 b449918f5a15 sshd[85]: error: Could not get shadow information for NOUSER
Feb 5 21:16:13 b449918f5a15 sshd[85]: Failed password for invalid user user from 10.24.0.30 port 55055 ssh2
Feb 5 21:16:13 b449918f5a15 sshd[85]: error: Received disconnect from 10.24.0.30 port 55055:13: Unable to authenticate [preauth]
Feb 5 21:16:13 b449918f5a15 sshd[85]: Disconnected from 10.24.0.30 port 55055 [preauth]

 

I have created the users.conf with users as:

user1:password:1001:100

 

I just want to be able to login with username and password where I have jailed the user to a folder. 
How can I fix it?

Link to comment
  • 3 weeks later...

To answer many of the latest SFTP questions:

Edit your users.conf file as you want it.

 

Then run: 

docker exec -it sftp rm /var/run/sftp/users.conf

substitute sftp if you gave your docker another name.

Restart docker afterwards and it will pick up the new users.conf file and create users as needed.

Link to comment

As of today I'm suddenly unable to use this. I keep getting an error  "No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting..." however, nothing has changed, just overnight it has stopped working. I double checked and the config files are still there, and if I edit the docker to add a path to /config/openvpn/ directly to the files it still shows they aren't there. I'm wondering if there was an update that may have broken a link somehow?

Link to comment

hi i am trying the qbittorrent image and? I am getting following error as its using IPv6 for some reason which I dont use:

Tue Feb 26 19:13:01 2019 TUN/TAP device tun0 opened
Tue Feb 26 19:13:01 2019 TUN/TAP TX queue length set to 100
Tue Feb 26 19:13:01 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=1
Tue Feb 26 19:13:01 2019 /sbin/ip link set dev tun0 up mtu 1500
Tue Feb 26 19:13:01 2019 /sbin/ip addr add dev tun0 10.x.x.x/16 broadcast xx.xx.255.255
Tue Feb 26 19:13:01 2019 /sbin/ip -6 addr add fdda:d0d0:cafe:1301::1006/64 dev tun0
RTNETLINK answers: Permission denied
Tue Feb 26 19:13:01 2019 Linux ip -6 addr add failed: external program exited with error status: 2

Tue Feb 26 19:13:01 2019 Exiting due to fatal error

How do I stop the container using IPv6?

Edited by nekromantik
Link to comment

hello i am having a issue accessing the web ui from LAN using default settings/port this is the logs:

2019-03-05 15:53:19.151069 [info] VPN_ENABLED defined as 'yes'
2019-03-05 15:53:19.194490 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/gw3.ewr1.slickvpn.com.ovpn
dos2unix: converting file /config/openvpn/gw3.ewr1.slickvpn.com.ovpn to Unix format...
2019-03-05 15:53:19.226323 [info] VPN remote line defined as 'gw3.ewr1.slickvpn.com 443 udp'
2019-03-05 15:53:19.253372 [info] VPN_REMOTE defined as 'gw3.ewr1.slickvpn.com'
2019-03-05 15:53:19.281987 [info] VPN_PORT defined as '443'
2019-03-05 15:53:19.321838 [info] VPN_PROTOCOL defined as 'udp'
2019-03-05 15:53:19.349631 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-03-05 15:53:19.376320 [info] LAN_NETWORK defined as '192.168.0.0/24'
2019-03-05 15:53:19.402173 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
2019-03-05 15:53:19.428185 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-03-05 15:53:19.455175 [info] Adding 8.8.8.8 to resolv.conf
2019-03-05 15:53:19.483401 [info] Adding 8.8.4.4 to resolv.conf
2019-03-05 15:53:19.507962 [info] Starting OpenVPN...
Tue Mar 5 15:53:19 2019 WARNING: file 'credentials.conf' is group or others accessible

Tue Mar 5 15:53:19 2019 OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 5 2018
Tue Mar 5 15:53:19 2019 library versions: OpenSSL 1.1.0g 2 Nov 2017, LZO 2.08
Tue Mar 5 15:53:19 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]50.116.54.120:443
Tue Mar 5 15:53:19 2019 UDP link local: (not bound)
Tue Mar 5 15:53:19 2019 UDP link remote: [AF_INET]50.116.54.120:443
Tue Mar 5 15:53:19 2019 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

Tue Mar 5 15:53:20 2019 [VPN] Peer Connection Initiated with [AF_INET]50.116.54.120:443
Tue Mar 5 15:53:21 2019 TUN/TAP device tun0 opened
Tue Mar 5 15:53:21 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Tue Mar 5 15:53:21 2019 /sbin/ip link set dev tun0 up mtu 1500
Tue Mar 5 15:53:21 2019 /sbin/ip addr add dev tun0 local 10.10.8.10 peer 10.10.8.9
Tue Mar 5 15:53:21 2019 Initialization Sequence Completed
2019-03-05 15:53:24.542961 [info] WebUI port defined as 8080
2019-03-05 15:53:24.570092 [info] LAN Network defined as 192.168.0.0/24
2019-03-05 15:53:24.597878 [info] Default gateway defined as 10.10.8.9
Error: Nexthop has invalid gateway.

2019-03-05 15:53:24.624012 [info] ip route defined as follows...
--------------------
default via 10.10.8.9 dev tun0
10.10.8.1 via 10.10.8.9 dev tun0
10.10.8.9 dev tun0 proto kernel scope link src 10.10.8.10
50.116.54.120 via 192.168.0.254 dev eth0
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.1
--------------------
iptable_mangle 16384 1
ip_tables 24576 3 iptable_filter,iptable_nat,iptable_mangle
2019-03-05 15:53:24.653135 [info] iptable_mangle support detected, adding fwmark for tables
2019-03-05 15:53:24.706753 [info] Docker network defined as 192.168.0.0/24
2019-03-05 15:53:24.764238 [info] Incoming connections port defined as 8999
2019-03-05 15:53:24.793615 [info] iptables defined as follows...
--------------------
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -d 192.168.0.0/24 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 443 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 8999 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 192.168.0.0/24 -d 192.168.0.0/24 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 443 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 8999 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
--------------------
Adding 100 group
groupadd: GID '100' already exists
Adding 99 user
useradd: UID 99 is not unique
2019-03-05 15:53:24.835057 [info] UMASK defined as '002'
2019-03-05 15:53:24.869162 [info] Starting qBittorrent daemon...
Logging to /config/qBittorrent/data/logs/qbittorrent-daemon.log.
2019-03-05 15:53:25.899837 [info] qBittorrent PID: 189
2019-03-05 15:53:25.903727 [info] Started qBittorrent daemon successfully...

any ideas as to what might be going on?

Link to comment
  • 1 month later...
On 2/26/2019 at 7:17 PM, nekromantik said:

hi i am trying the qbittorrent image and? I am getting following error as its using IPv6 for some reason which I dont use:


Tue Feb 26 19:13:01 2019 TUN/TAP device tun0 opened
Tue Feb 26 19:13:01 2019 TUN/TAP TX queue length set to 100
Tue Feb 26 19:13:01 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=1
Tue Feb 26 19:13:01 2019 /sbin/ip link set dev tun0 up mtu 1500
Tue Feb 26 19:13:01 2019 /sbin/ip addr add dev tun0 10.x.x.x/16 broadcast xx.xx.255.255
Tue Feb 26 19:13:01 2019 /sbin/ip -6 addr add fdda:d0d0:cafe:1301::1006/64 dev tun0
RTNETLINK answers: Permission denied
Tue Feb 26 19:13:01 2019 Linux ip -6 addr add failed: external program exited with error status: 2

Tue Feb 26 19:13:01 2019 Exiting due to fatal error

How do I stop the container using IPv6?

 

Hi @nekromantik

I just had a similar problem in the transmission_vpn docker where it would constantly restart with the 'RTNETLINK answers: Permission denied' error. Solved it following this guide  https://stackoverflow.com/questions/50600116/ipv6-with-openvpn-in-docker  by editing the settings of the docker, while changing from the 'Basic View' to the 'Advanced View' of the settings and then adding to the part 'Extra Parameters:' this: '--sysctl net.ipv6.conf.all.disable_ipv6=0 ' . After applying the docker started without problems. Hope it helps.

Link to comment
On 4/5/2019 at 10:31 PM, cen said:

 

Hi @nekromantik

I just had a similar problem in the transmission_vpn docker where it would constantly restart with the 'RTNETLINK answers: Permission denied' error. Solved it following this guide  https://stackoverflow.com/questions/50600116/ipv6-with-openvpn-in-docker  by editing the settings of the docker, while changing from the 'Basic View' to the 'Advanced View' of the settings and then adding to the part 'Extra Parameters:' this: '--sysctl net.ipv6.conf.all.disable_ipv6=0 ' . After applying the docker started without problems. Hope it helps.

thanks but I given up as even after I got it working it would not play well with radarr and sonarr so went back to rutorrent

Link to comment

Good evening. I'm having a problem with Deluge and qBitTorrent.

I seem to be unable to connect to either of them via reverse proxy (This started happening a couple of days ago, unifi is also having this issue.)

Sonarr seems to be unable to connect to qbit, but radarr can connect to deluge, both deluge and qbit can be accessed by their respective ipaddress:port. Any help is appreciated.

I am also able to ping deluge and qbit from the console of other dockers both by container name and by IP address.

Setting the VPN to No allows the reverse proxy and the sonarr to connect.

 

THIS DOESNT SEEM TO BE A DOCKER ISSUE!

I've dropped unraid back to 6.6.6 and all is working as expected, any idea why 6.6.7 is producing this behaviour?

Edited by karldonteljames
Link to comment
  • 1 month later...

Hello,

I'm having an issue getting Sonarr to communicate with qBittorrentvpn.

Here is my qbittorrent docker logs and run command:

docker run -d --name='qbittorrentvpn' --net='br0' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TCP_PORT_8080'='8180' -e 'TCP_PORT_8999'='8999' -e 'UDP_PORT_8999'='8999' -e 'WEBUI_PORT'='8180' -e 'INCOMING_PORT'='8999' -e 'VPN_ENABLED'='yes' -e 'VPN_USERNAME'=<username> -e 'VPN_PASSWORD'=<password> -e 'LAN_NETWORK'='10.1.20.0/24' -e 'NAME_SERVERS'='8.8.8.8,8.8.4.4' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='002' -v '/mnt/user/appdata/downloads/':'/downloads':'rw' -v '/mnt/user/appdata/qbittorrentvpn':'/config':'rw' 'markusmcnugen/qbittorrentvpn'

Both containers are up and running and appear to be working correctly, I just can't get sonarr to talk with qbittorrentvpn. Any ideas? I'm not sure if I'm putting in the wrong address for the Host (in the sonarr -> add client window) or if its because of the custom network for qbittorrent?

Link to comment
  • 5 months later...
On 5/13/2019 at 3:44 PM, PISTOL_CUPCAKES said:

Hello,

I'm having an issue getting Sonarr to communicate with qBittorrentvpn.

Here is my qbittorrent docker logs and run command:


docker run -d --name='qbittorrentvpn' --net='br0' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TCP_PORT_8080'='8180' -e 'TCP_PORT_8999'='8999' -e 'UDP_PORT_8999'='8999' -e 'WEBUI_PORT'='8180' -e 'INCOMING_PORT'='8999' -e 'VPN_ENABLED'='yes' -e 'VPN_USERNAME'=<username> -e 'VPN_PASSWORD'=<password> -e 'LAN_NETWORK'='10.1.20.0/24' -e 'NAME_SERVERS'='8.8.8.8,8.8.4.4' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='002' -v '/mnt/user/appdata/downloads/':'/downloads':'rw' -v '/mnt/user/appdata/qbittorrentvpn':'/config':'rw' 'markusmcnugen/qbittorrentvpn'

Both containers are up and running and appear to be working correctly, I just can't get sonarr to talk with qbittorrentvpn. Any ideas? I'm not sure if I'm putting in the wrong address for the Host (in the sonarr -> add client window) or if its because of the custom network for qbittorrent?

I had a similar issue.  I was able to fix it by going into Sonarr docker config and under network type bridge to br:0...

 

Network Type: Custom : br0

 

After that I was able to see qBittorrentVPN from Sonarr.

 

Source: First and Second post.

 

Link to comment
  • 2 weeks later...

So i am trying to get qBittorrent VPN setup but i am running into some issues. The container and application come up, and i can access the webui. I can open a console into the container and check that i have a valid IP address through the VPN. qBittorrent however never finds any peers or shows any signs that it can contact the outside world. What am i doing wrong?

docker create --name='qbittorrentvpn' --net='bridge' --log-opt max-size='50m' --log-opt max-file='3' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'WEBUI_PORT'='7070' -e 'INCOMING_PORT'='8999' -e 'VPN_ENABLED'='yes' -e 'VPN_USERNAME'='' -e 'VPN_PASSWORD'='' -e 'LAN_NETWORK'='192.168.0.0/24' -e 'NAME_SERVERS'='8.8.8.8,8.8.4.4,1.1.1.1' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='002' -p '7070:7070/tcp' -p '8999:8999/tcp' -p '8999:8999/udp' -v '/mnt/user/Video_Conversion/bit':'/downloads':'rw' -v '/mnt/user/appdata/qbittorrentvpn':'/config':'rw' 'markusmcnugen/qbittorrentvpn' 
2019-11-21 04:03:36.501191 [info] VPN_ENABLED defined as 'yes'
2019-11-21 04:03:36.533662 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn
dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format...
2019-11-21 04:03:36.563569 [info] VPN remote line defined as 'example.com 1194'
2019-11-21 04:03:36.593125 [info] VPN_REMOTE defined as 'example.com'
2019-11-21 04:03:36.619303 [info] VPN_PORT defined as '1194'
2019-11-21 04:03:36.643870 [info] VPN_PROTOCOL defined as 'udp'
2019-11-21 04:03:36.668103 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-11-21 04:03:36.692478 [info] LAN_NETWORK defined as '192.168.0.0/24'
2019-11-21 04:03:36.718937 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4,1.1.1.1'
2019-11-21 04:03:36.744692 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-11-21 04:03:36.769547 [info] Adding 8.8.8.8 to resolv.conf
2019-11-21 04:03:36.795720 [info] Adding 8.8.4.4 to resolv.conf
2019-11-21 04:03:36.821595 [info] Adding 1.1.1.1 to resolv.conf
2019-11-21 04:03:36.845036 [info] Starting OpenVPN...
Thu Nov 21 04:03:36 2019 OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 5 2018
Thu Nov 21 04:03:36 2019 library versions: OpenSSL 1.1.0g 2 Nov 2017, LZO 2.08
Thu Nov 21 04:03:36 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]172.246.117.2:1194
Thu Nov 21 04:03:36 2019 UDP link local: (not bound)
Thu Nov 21 04:03:36 2019 UDP link remote: [AF_INET]172.246.117.2:1194
Thu Nov 21 04:03:37 2019 [example.com] Peer Connection Initiated with [AF_INET]172.246.117.2:1194
Thu Nov 21 04:03:43 2019 TUN/TAP device tun0 opened
Thu Nov 21 04:03:43 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Thu Nov 21 04:03:43 2019 /sbin/ip link set dev tun0 up mtu 1500
Thu Nov 21 04:03:43 2019 /sbin/ip addr add dev tun0 local 10.200.0.22 peer 10.200.0.21
Thu Nov 21 04:03:43 2019 Initialization Sequence Completed
2019-11-21 04:03:43.885837 [info] WebUI port defined as 7070
2019-11-21 04:03:43.911684 [info] LAN Network defined as 192.168.0.0/24
2019-11-21 04:03:43.937177 [info] Default gateway defined as 172.17.0.1
2019-11-21 04:03:43.963338 [info] ip route defined as follows...
--------------------
0.0.0.0/1 via 10.200.0.21 dev tun0
default via 172.17.0.1 dev eth0
10.200.0.1 via 10.200.0.21 dev tun0 metric 1
10.200.0.21 dev tun0 proto kernel scope link src 10.200.0.22
128.0.0.0/1 via 10.200.0.21 dev tun0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.10
172.246.117.2 via 172.17.0.1 dev eth0
192.168.0.0/24 via 172.17.0.1 dev eth0
--------------------
iptable_mangle 16384 1
ip_tables 24576 3 iptable_filter,iptable_nat,iptable_mangle
2019-11-21 04:03:43.992738 [info] iptable_mangle support detected, adding fwmark for tables
2019-11-21 04:03:44.033458 [info] Docker network defined as 172.17.0.0/16
2019-11-21 04:03:44.089384 [info] Incoming connections port defined as 8999
2019-11-21 04:03:44.119328 [info] iptables defined as follows...
--------------------
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1194 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 7070 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 7070 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 8999 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1194 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 7070 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 7070 -j ACCEPT
-A OUTPUT -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 8999 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
--------------------
Adding 100 group
groupadd: GID '100' already exists
Adding 99 user
useradd: UID 99 is not unique
2019-11-21 04:03:44.168476 [info] UMASK defined as '002'
2019-11-21 04:03:44.201173 [info] Starting qBittorrent daemon...
Logging to /config/qBittorrent/data/logs/qbittorrent-daemon.log.
2019-11-21 04:03:45.233003 [info] qBittorrent PID: 203
2019-11-21 04:03:45.237872 [info] Started qBittorrent daemon successfully...
(N) 2019-11-21T04:03:44 - qBittorrent v4.1.5 started
(I) 2019-11-21T04:03:44 - qBittorrent is trying to listen on any interface port: 8999
(N) 2019-11-21T04:03:44 - Peer ID: -qB4150-
(N) 2019-11-21T04:03:44 - HTTP User-Agent is 'qBittorrent/4.1.5'
(I) 2019-11-21T04:03:44 - DHT support [ON]
(I) 2019-11-21T04:03:44 - Local Peer Discovery support [OFF]
(I) 2019-11-21T04:03:44 - PeX support [ON]
(I) 2019-11-21T04:03:44 - Anonymous mode [OFF]
(I) 2019-11-21T04:03:44 - Encryption support [ON]
(I) 2019-11-21T04:03:44 - Embedded Tracker [OFF]
(I) 2019-11-21T04:03:44 - GeoIP database loaded. Type: GeoLite2-Country. Build time: Tue Nov 12 21:09:59 2019.
(N) 2019-11-21T04:03:44 - Using built-in Web UI.
(N) 2019-11-21T04:03:44 - Web UI translation for selected locale (en) has been successfully loaded.
(N) 2019-11-21T04:03:44 - Web UI: Now listening on IP: *, port: 7070
(C) 2019-11-21T04:03:44 - Queue positions were corrected in 2 resume files
(I) 2019-11-21T04:03:44 - qBittorrent is successfully listening on interface :: port: TCP/8999
(I) 2019-11-21T04:03:44 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/8999
(I) 2019-11-21T04:03:44 - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/8999
(N) 2019-11-21T04:03:44 - 'linuxmint-17-cinnamon-32bit-v2.iso' restored.
(N) 2019-11-21T04:03:44 - 'checkmyiptorrent' restored.

 

Link to comment
  • 3 weeks later...

I've noticed that the WebUi seems to be a reoccurring issue over the last few years in this thread, So I'll post here and maybe someone can help me understand what's going on.

 

After starting Qbittorrent i cannot log into the WebUi.  After checking the log, I can see that it accepts my openvpn login/password, and assigns me an Ip address.  "Started qBittorrent daemon successfully..." .. But No WebUi.  So I disabled Vpn login and I Vuala! Webui works.  so I log in, open Console> and manually run openvpn my.ovpn.  At this point it uses the cridentials.conf and logs me into my vpn.  However I have to keep the console window open or I lose vpn connection.  When I reenable vpn in the config, No more WebUi.

 

ideas??

Link to comment
  • 2 weeks later...

Hi!

 

I was playing around with markusmcnugen/qbittorrentvpn and i cannot get vpn to connect when not having the docker run in "privileged" mode, i feel like i don't want anything to run with elevated permissions unless i really really really have to.

 

Is there any workaround to get the vpn to work without using the docker in privileged mode?

 

Thank you!

Link to comment
  • 4 weeks later...
On 12/19/2019 at 1:50 AM, je82 said:

Hi!

 

I was playing around with markusmcnugen/qbittorrentvpn and i cannot get vpn to connect when not having the docker run in "privileged" mode, i feel like i don't want anything to run with elevated permissions unless i really really really have to.

 

Is there any workaround to get the vpn to work without using the docker in privileged mode?

 

Thank you!

Nope, with the way docker and VPNs work it has to be privileged mode due to the host sharing the kernel space with the docker.

Link to comment
13 hours ago, vyreks said:

Hi,
Recently you updated the docker to version 4.2.1 which broke most (if not all) private trackers as they don't have 4.2.X whitelisted yet. Could you create a tag on dockerhub for latest version on 4.1.X please?

I will see if I can do this over the weekend. I usually just build from dockerhub with auto triggers and call it good but I have a VM I use for building as well.

Link to comment
  • 3 weeks later...

I was reading through the documentation regarding the sFTP docker and it appears i have to specify the home path for each user directly in the startup string of the docker container. Does this mean i can only have 1 user with 1 home path per SFTP container and not multiple different users with multiple different home paths?

 

image.png.0a20d0c6459e31b19389e16776be9623.png

Link to comment
  • 2 months later...

Hello.

 

I installed sftp on unraid.  Got the container to start after going through unraid console and manually adding a user.  However; when I sftp (using putty) I authenticate and then putty just closes.

Nothing in the sftp container logs that i can see, just that I had successfully authenticated.

Apr 6 00:45:12 b34201513c63 sshd[52]: Server listening on 0.0.0.0 port 22.
Apr 6 00:45:12 b34201513c63 sshd[52]: Server listening on :: port 22.
Apr 6 00:46:23 b34201513c63 sshd[73]: Accepted password for <username> from 10.180.5.50 port 59361 ssh2

the first two lines above; do I need to configure this container further?

Edited by repomanz
updated info
Link to comment
  • 4 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.