[[Support] binhex - rTorrentVPN]

Thank you very much for information I also returned to "rtorrent-ps" because it was impossible to get "rtorrent" to work with AirVPN. Good luck @binhex

[[Support] binhex - rTorrentVPN]

33 minutes ago, binhex said:

It was released yesterday if you want to pick up the new image then click on force update

Sent from my CLT-L09 using Tapatalk
 

Txh very much, it's ok now ! Good Job !

[[Support] binhex - rTorrentVPN]

Hello @binhex, Do you have any idea when the image will be released?  Thank you very much for your work !

[[Support] binhex - rTorrentVPN]

Thank you very much for your reply, I look forward to the update

[[Support] binhex - rTorrentVPN]

Hello. Since this morning I have had an error message in the supervisor.log. Having issues resolving name 'www.google.com', sleeping before retry ... Everything worked fine yesterday. I use AirVPN and the following configuration:

      - VPN_ENABLED=yes
      - VPN_PROV=airvpn
      - ENABLE_PRIVOXY=no
      - ENABLE_FLOOD=no
      - ENABLE_AUTODL_IRSSI=no
      - ENABLE_RPC2=yes
      - ENABLE_RPC2_AUTH=yes
      - ENABLE_WEBUI_AUTH=yes
      - RPC2_USER=clusmi
      - RPC2_PASS=MyVeryHARDpASSWORD
      - WEBUI_USER=clusmi
      - WEBUI_PASS=MyVeryHARDpASSWORD
      - LAN_NETWORK=192.168.0.0/24
      - NAME_SERVERS=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
      - DEBUG=false
      - PHP_TZ=Europe/Paris
      - UMASK=000
      - PUID=1500
      - PGID=1500

Do you have an idea?

 

Txh very much

[[Support] binhex - rTorrentVPN]

Hello,

 

I have found another solution, for me is the best solution if you use proxmox and lxc.

Edit post :

 

Bye

[[Support] binhex - rTorrentVPN]

Hello @binhex

 

I found the solution and I post it here for the people in my case.

Under our proxmox host:  

nano /etc/pve/lxc/XXX.conf (XXX is the ID of the proxmox CT)

Add at the end:

lxc.autodev: 1
lxc.hook.autodev: sh -c "mknod -m 0666 ${LXC_ROOTFS_MOUNT}/dev/fuse c 10 229"
lxc.cgroup.devices.allow: c 10:200 rwm
lxc.apparmor.profile: unconfined

And :

nano /etc/modules

 

add iptables if missing

 

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

loop

# Iptables modules to be loaded for the OpenVZ container
ipt_REJECT
ipt_recent
ipt_owner
ipt_REDIRECT
ipt_tos
ipt_TOS
ipt_LOG
ip_conntrack
ipt_limit
ipt_multiport
iptable_filter
iptable_mangle
ipt_TCPMSS
ipt_tcpmss
ipt_ttl
ipt_length
ipt_state
iptable_nat
ip_nat_ftp
ipt_MASQUERADE

 

Restart the proxmox host and restart container too. Access to rutorrent is OK from the outside. With this change, we allow the use of the iptable_mangle modprobe on the container.

Thank you for this great image @binhex.

A + and good luck!

[[Support] binhex - rTorrentVPN]

Yes, my proxmox is a real machine. This is not a virtual machine.

In my proxmox, I create a container dedicated to a seedbox, and I use your image docker with a VPN.

I have access to my interface rutorrent locally, but from outside my local network, not working

[[Support] binhex - rTorrentVPN]

Proxmox Container (lxc), not a Proxmox Virual machine (qemu).

I add "/sbin/modprobe iptable_mangle" in the file "go" on my host proxmox and on my container lxc, and after reboot, I still do not have access to my webui rutorrent from outside my local network Do you have an idea ?

[[Support] binhex - rTorrentVPN]

Hi binhex!  

 

I am in the same situation as superboki.  My container docker ‘rutorrentvpn’ runs under a proxmox CT.  iptable_mangle must be on my proxmox or on my CT?

 

Thank you !