Trevo525

January 5

I am fully aware that this is pretty old. I found it in my searches, so I am going to leave this for future searchers.

This method is nice because the VPN is setup on the OS level, not in a container. That allows you to see some stats through the unifi interface pretty quickly.

February 12, 2023

I'll start off by saying that I have read the big bold text on your guide.

Quote

ANY CONTAINER THAT GETS ROUTED THROUGH THIS CONTAINER WILL (BRIEFLY) USE YOUR REAL IP. THIS IS BECAUSE THE PASSTHROUGHVPN CONTAINER NEEDS TO ESTABLISH A CONNECTION WITH THE VPN FIRST. TILL THAT IS DONE, THE CONTAINER(S) YOU PASSTHROUGH THIS CONTAINER WILL EXPOSE YOUR REAL IP. DO NOT USE THIS CONTAINER IF YOU WISH TO EXPOSE YOUR REAL IP FOR NOT A SINGLE SECOND. NORMALLY ESTABLISHING A VPN CONNECTION WILL TAKE A COUPLE SECONDS. HOWEVER, IF YOUR VPN PROVIDER IS UNREACHABLE, IT WILL KEEP ON USING YOUR REAL IP. This is different than using any of my other 'vpn' containers, since with those the application (for example qBittorrent or Jackett) will start AFTER establishing the connection. By using this container, you will have a connection before connecting to the VPN.

I have been using a few of these referenced VPN-bundled containers for a while. My VPN provider only offers three client connections at a time though. So, I would like change my setup model to use your container or one like it for the connection and use normal images connected to it. But, more than one of my containers will try to do their thing immediately and I don't want them to EVER use my public IP. Especially if my VPN Provider is unreachable. I don't want it to just keep trying

Quote

THE PASSTHROUGHVPN CONTAINER NEEDS TO ESTABLISH A CONNECTION WITH THE VPN FIRST. TILL THAT IS DONE, THE CONTAINER(S) YOU PASSTHROUGH THIS CONTAINER WILL EXPOSE YOUR REAL IP.

I've been reading through the start.sh and iptables.sh files and I was curious why we can not just use IPTables to block all outgoing packets on the docker bridge, except by either wireguard or openvpn? I am not too knowledgeable on how all of this works, so please correct me if I am misunderstanding something. It seems like if you were to block all outgoing connections in start.sh after checking if VPN_ENABLED == "yes",

if [[ $VPN_ENABLED == "yes" ]]; then
	# Check if VPN_TYPE is set.
	if [[ -z "${VPN_TYPE}" ]]; then

Then you could allow wireguard in an iptable before it's started or allow openvpn before it's started in the code below.

if [[ $VPN_ENABLED == "yes" ]]; then
	if [[ "${VPN_TYPE}" == "openvpn" ]]; then
		echo "[INFO] Starting OpenVPN..." | ts '%Y-%m-%d %H:%M:%.S'
		cd /config/openvpn
		exec openvpn --pull-filter ignore route-ipv6 --pull-filter ignore ifconfig-ipv6 --config "${VPN_CONFIG}" &
		#exec /bin/bash /etc/openvpn/openvpn.init start &
	else
		echo "[INFO] Starting WireGuard..." | ts '%Y-%m-%d %H:%M:%.S'
		cd /config/wireguard
		if ip link | grep -q `basename -s .conf $VPN_CONFIG`; then
			wg-quick down $VPN_CONFIG || echo "WireGuard is down already" | ts '%Y-%m-%d %H:%M:%.S' # Run wg-quick down as an extra safeguard in case WireGuard is still up for some reason
			sleep 0.5 # Just to give WireGuard a bit to go down
		fi
		wg-quick up $VPN_CONFIG
		#exec /bin/bash /etc/openvpn/openvpn.init start &
	fi
	exec /bin/bash /etc/passthrough/iptables.sh

Then you could keep the call to iptables.sh to finalize the iptables configuration once it is started successfully. That should block the passed through apps from using the public IP. Right?

Am I on to something here or not?

January 26, 2022

I must've joined and left in the past. I keep getting, "You are already a member of our Discord server.". Any help?

edit: I think I was able to find it. I didn't even know there was a discover feature in Discord. TIL.

January 25, 2022

21 minutes ago, trurl said:

Marvell controllers are NOT recommended but might work if you disable VT-d

Do they just go bad more often? Or is there a problem with their drivers? I just wonder because I've been using it for a while with no problems.

I found this guide:

I googled: Asmedia ASM1064 and found https://www.amazon.com/FebSmart-Expansion-System-ASMedia-Controller-FS-S4-Pro/dp/B097R6MQBT Would you suggest this?

Thanks for your time! I will try new SATA cables, hopefully tomorrow. But, if that controller seams to be causing the problem, I'll order a new one tonight.

January 24, 2022

First off, this is not a new install. It's been working without any changes for 2-3 years now. So, that makes me believe that it might be hardware failure. But, I checked the GUI today and saw that two of my disks had a little red 'x' where there is normally a green dot. I see 66 errors under both drives.

Following error under the logs of Disk 5 "ata11.00: exception Emask 0x0 SAct 0x10 SErr 0x0 action 0x6 frozen" here is the full log.

Jan 22 12:57:59 TrevNas2 kernel: ata11: SATA max UDMA/133 abar m2048@0xfbabe000 port 0xfbabe200 irq 42
Jan 22 12:57:59 TrevNas2 kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 22 12:57:59 TrevNas2 kernel: ata11.00: ATA-9: WDC WD80EMAZ-00WJTA0, 7HJTUTUF, 83.H0A83, max UDMA/133
Jan 22 12:57:59 TrevNas2 kernel: ata11.00: 15628053168 sectors, multi 0: LBA48 NCQ (depth 32), AA
Jan 22 12:57:59 TrevNas2 kernel: ata11.00: configured for UDMA/133
Jan 22 12:57:59 TrevNas2 kernel: sd 11:0:0:0: [sdk] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
Jan 22 12:57:59 TrevNas2 kernel: sd 11:0:0:0: [sdk] 4096-byte physical blocks
Jan 22 12:57:59 TrevNas2 kernel: sd 11:0:0:0: [sdk] Write Protect is off
Jan 22 12:57:59 TrevNas2 kernel: sd 11:0:0:0: [sdk] Mode Sense: 00 3a 00 00
Jan 22 12:57:59 TrevNas2 kernel: sd 11:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 22 12:57:59 TrevNas2 kernel: sdk: sdk1
Jan 22 12:57:59 TrevNas2 kernel: sd 11:0:0:0: [sdk] Attached SCSI removable disk
Jan 22 12:58:36 TrevNas2 emhttpd: WDC_WD80EMAZ-00WJTA0_7HJTUTUF (sdk) 512 15628053168
Jan 22 12:58:36 TrevNas2 kernel: mdcmd (6): import 5 sdk 64 7814026532 0 WDC_WD80EMAZ-00WJTA0_7HJTUTUF
Jan 22 12:58:36 TrevNas2 kernel: md: import disk5: (sdk) WDC_WD80EMAZ-00WJTA0_7HJTUTUF size: 7814026532
Jan 22 12:58:36 TrevNas2 emhttpd: read SMART /dev/sdk
Jan 22 12:58:41 TrevNas2 emhttpd: shcmd (28): echo 128 > /sys/block/sdk/queue/nr_requests
Jan 22 12:58:47 TrevNas2 s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl
Jan 24 02:15:46 TrevNas2 kernel: ata11.00: exception Emask 0x0 SAct 0x10 SErr 0x0 action 0x6 frozen
Jan 24 02:15:46 TrevNas2 kernel: ata11.00: failed command: READ FPDMA QUEUED
Jan 24 02:15:46 TrevNas2 kernel: ata11.00: cmd 60/08:20:98:6c:ac/00:00:0d:01:00/40 tag 4 ncq dma 4096 in
Jan 24 02:15:46 TrevNas2 kernel: ata11.00: status: { DRDY }
Jan 24 02:15:46 TrevNas2 kernel: ata11: hard resetting link
Jan 24 02:15:56 TrevNas2 kernel: ata11: softreset failed (1st FIS failed)
Jan 24 02:15:56 TrevNas2 kernel: ata11: hard resetting link

Disk 6 had no such errors but still didn't show up in this at all.

Jan 22 12:57:59 TrevNas2 kernel: ata12: SATA max UDMA/133 abar m2048@0xfbabe000 port 0xfbabe280 irq 42
Jan 22 12:57:59 TrevNas2 kernel: ata12: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 22 12:57:59 TrevNas2 kernel: ata12.00: ATA-9: WDC WD80EMAZ-00WJTA0, JEGVK2AN, 83.H0A83, max UDMA/133
Jan 22 12:57:59 TrevNas2 kernel: ata12.00: 15628053168 sectors, multi 0: LBA48 NCQ (depth 32), AA
Jan 22 12:57:59 TrevNas2 kernel: ata12.00: configured for UDMA/133
Jan 22 12:57:59 TrevNas2 kernel: sd 12:0:0:0: [sdl] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
Jan 22 12:57:59 TrevNas2 kernel: sd 12:0:0:0: [sdl] 4096-byte physical blocks
Jan 22 12:57:59 TrevNas2 kernel: sd 12:0:0:0: [sdl] Write Protect is off
Jan 22 12:57:59 TrevNas2 kernel: sd 12:0:0:0: [sdl] Mode Sense: 00 3a 00 00
Jan 22 12:57:59 TrevNas2 kernel: sd 12:0:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 22 12:57:59 TrevNas2 kernel: sdl: sdl1
Jan 22 12:57:59 TrevNas2 kernel: sd 12:0:0:0: [sdl] Attached SCSI removable disk
Jan 22 12:58:36 TrevNas2 emhttpd: WDC_WD80EMAZ-00WJTA0_JEGVK2AN (sdl) 512 15628053168
Jan 22 12:58:36 TrevNas2 kernel: mdcmd (7): import 6 sdl 64 7814026532 0 WDC_WD80EMAZ-00WJTA0_JEGVK2AN
Jan 22 12:58:36 TrevNas2 kernel: md: import disk6: (sdl) WDC_WD80EMAZ-00WJTA0_JEGVK2AN size: 7814026532
Jan 22 12:58:36 TrevNas2 emhttpd: read SMART /dev/sdl
Jan 22 12:58:41 TrevNas2 emhttpd: shcmd (29): echo 128 > /sys/block/sdl/queue/nr_requests
Jan 22 12:58:47 TrevNas2 s3_sleep: included disks=sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl

I found this topic on it:

But I believe it might be different. Their error seems to be for a bad parity check and mine isn't even able to do a parity check. From my understanding.

I also found this one:

But, I'm not sure what to take from it..

I have attached the diagnostics report. I am not sure where to go from here.

trevnas2-diagnostics-20220124-1717.zip

March 13, 2021

Request for advice. I want to host multiple containers that use the same port. Can I somehow change the port from one container to another?

March 10, 2021

On 3/5/2021 at 11:32 AM, m0lle said:

I have the latest update from 2 days ago and I still have the issue where a bunch of the plugins wont work. Anyone else also experiencing this?

Me too. I rolled it back but I saw that Binhex was actively fixed some other issues so I tried updating to the latest again just to see if it was fixed but it still is broken for me. It's seeding and all but the plugins are broken for me.

March 2, 2021

49 minutes ago, beinghitesh said:

While we wait for @binhex to investigate the bug, you can pull the previous release as that was working fine.

Add ":rtorrent-ps-1.1.r54.ga787dd9-1-29" after "binhex/arch-rtorrentvpn". This will pull this specific release. If you ever want to go back to the latest release, you can use ":latest" or just "binhex/arch-rtorrentvpn". You can check the releases here https://github.com/binhex/arch-rtorrentvpn/releases.

Hope this helps.

Good temporary solution. Thank you!

March 1, 2021

Out of nowhere my container is messing up. I've had it running with no problem for months and now I am getting a bunch of errors.

[01.03.2021 08:56:39] WebUI started.
[01.03.2021 08:56:42] _cloudflare: Plugin will not work. rTorrent user can't access external program (python).
[01.03.2021 08:56:42] _task: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] autotools: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] create: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] datadir: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] history: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] loginmgr: Some functionality will be unavailable. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] ratio: Some functionality will be unavailable. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] retrackers: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] rss: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] rutracker_check: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] scheduler: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] trafic: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] unpack: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] xmpp: Plugin will not work. rTorrent user can't access external program (php).
[01.03.2021 08:56:42] _task: Plugin will not work. rTorrent user can't access external program (pgrep).
[01.03.2021 08:56:42] mediainfo: Plugin will not work. rTorrent user can't access external program (mediainfo).
[01.03.2021 08:56:42] rss: Some functionality will be unavailable. rTorrent user can't access external program (curl).
[01.03.2021 08:56:42] screenshots: Plugin will not work. rTorrent user can't access external program (ffmpeg).
[01.03.2021 08:56:42] spectrogram: Plugin will not work. rTorrent user can't access external program (sox).
[01.03.2021 11:40:31] The request to rTorrent has timed out.

That is from the log of the webui. Is anyone else having this issue or is it just me?

edit: I should also add that I can no longer use those plugins. So i can't move files in rutorrent because the plugin that adds "save to" to the right click menu is not loaded. It's pretty frustrating because I have been moving files recently and this has brought that to a full stop.

Trevo525

Posts

Joined

Last visited

Content Type

Profiles

Forums

Downloads

Store

Gallery

Bug Reports

Documentation

Landing

Posts posted by Trevo525

Routing Containers through WireGuard

[Support] dyonr - passthroughvpn

Unraid Official Discord Server

two of my nine disks have errors.

two of my nine disks have errors.

[Support] dyonr - passthroughvpn

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN

[Support] binhex - rTorrentVPN