spgill

I've been using docker-compose successfully for a few weeks now, but I'm curious (to those that also use it) what is your strategy for auto-starting containers on boot / on array start? It's not a huge imposition to log in and do a `docker-compose up -d` in the rare instance when my server reboots, but it would be nice for it to be more hands-off.

Hello all! Running latest Unraid stable build (v6.8.2) with the latest Dynamix WireGuard plugin (2020.02.23) and have had an intermittent issue with my WireGuard tunnel. The tunnel uses mostly default config settings, with one peer set to "Remote Access to LAN". The singular peer is a MacBook Pro using the WireGuard app. The problem that arises is immediately after activating the tunnel on the client, I can momentarily access LAN clients like I should, but if I try to transfer (what seems like) more than a few hundred kilobytes of data, the connection immediately halts and becomes unresponsive and I am unable to connect for another few minutes. I can also see in the VPN config page that there was indeed an initial handshake and that a small amount of data was exchanged. Example; after activating the tunnel, I can open an SSH connection and run a few commands, but if I try to transfer a file over SFTP or anything else, the tunnel will "collapse" after less than a second. Note: changing the MTU between auto and several common values did not seem to have any impact. In the client log, I see over and over after the "collapse"; 2020-02-24 12:29:35.611 [NET] peer(I4Hj…t3Ro) - Retrying handshake because we stopped hearing back after 15 seconds Does anyone have any clue what may be causing an issue like this?? I will post my tunnel and peer configurations below. Any insight would be greatly appreciated server: [Interface] #Home Tunnel PrivateKey=<redacted> Address=10.253.0.1 ListenPort=5182 PostUp=logger -t wireguard 'Tunnel WireGuard-wg0 started' PostUp=iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE PostDown=logger -t wireguard 'Tunnel WireGuard-wg0 stopped' PostDown=iptables -t nat -D POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE [Peer] #MBP LAN Access PublicKey=<redacted> PresharedKey=<redacted> AllowedIPs=10.253.0.2 peer: [Interface] #MBP LAN Access PrivateKey=<redacted> Address=10.253.0.2/32 DNS=192.168.86.1 [Peer] #Home Tunnel PresharedKey=<redacted> PublicKey=<redacted> Endpoint=<my external ip>:5182 AllowedIPs=10.253.0.1/32, 192.168.86.0/24

Running latest Unraid stable build (v6.8.2) with the latest Dynamix WireGuard plugin (2020.02.23) and have had an intermittent issue with my WireGuard tunnel. The tunnel uses mostly default config settings, with one peer set to "Remote Access to LAN". The singular peer is a MacBook Pro using the WireGuard app. The problem that arises is immediately after activating the tunnel on the client, I can momentarily access LAN clients like I should, but if I try to transfer (what seems like) more than a few hundred kilobytes of data, the connection immediately halts and becomes unresponsive and I am unable to connect for another few minutes. I can also see in the VPN config page that there was indeed an initial handshake and that a small amount of data was exchanged. Example; after activating the tunnel, I can open an SSH connection and run a few commands, but if I try to transfer a file over SFTP or anything else, the tunnel will "collapse" after less than a second. Note: changing the MTU between auto and several common values did not seem to have any impact. In the client log, I see over and over after the "collapse"; 2020-02-24 12:29:35.611 [NET] peer(I4Hj…t3Ro) - Retrying handshake because we stopped hearing back after 15 seconds Does anyone have any clue what may be causing an issue like this?? I will post my tunnel and peer configurations below. Any insight would be greatly appreciated server: [Interface] #Home Tunnel PrivateKey=<redacted> Address=10.253.0.1 ListenPort=5182 PostUp=logger -t wireguard 'Tunnel WireGuard-wg0 started' PostUp=iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE PostDown=logger -t wireguard 'Tunnel WireGuard-wg0 stopped' PostDown=iptables -t nat -D POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE [Peer] #MBP LAN Access PublicKey=<redacted> PresharedKey=<redacted> AllowedIPs=10.253.0.2 peer: [Interface] #MBP LAN Access PrivateKey=<redacted> Address=10.253.0.2/32 DNS=192.168.86.1 [Peer] #Home Tunnel PresharedKey=<redacted> PublicKey=<redacted> Endpoint=<my external ip>:5182 AllowedIPs=10.253.0.1/32, 192.168.86.0/24

I'm having the same experience mentioned here while trying to pull images from my GitHub-based repository. Unraid will never show that an update is available, but if I "force update" it will pull the changes just fine. Having this feature work like expected for private repos would be a wonderful addition. 😌

Pitching in my two cents... Relatively new Unraid user here experiencing the exact same symptoms after upgrading from a 6.6.x release to 6.7.2. Considering rolling back until this is fixed because it is crippling my system. My hardware is a Gigabyte GA-F2A88XM-D3HP motherboard, with an AMD A10-7860K CPU, and using the chipset SATA controller (AMD A88X) for my array. I have an attached LSI PCIe SAS card, but the problems didn't start until long after I installed it, and besides the only device plugged into it is a SAS tape drive which is turned off most of the time.