bearattack
Members
-
Joined
-
Last visited
-
Can you elaborate on this? I'm having the same issue.
-
I'm having a strange issue with FileBot mounting CIFS shares to /storage. It seems on a fresh reboot of Unraid, FileBot decides not to mount the CIFS share. I see the log line: [filebot-info] STORAGE: btrfs [/] @ 16 GB | fuse.shfs [/config] @ 1.9 TB | btrfs [/output] @ 16 GB | btrfs [/watch] @ 16 GB Simply restarting the container fixes the issue, and I see the log line: [filebot-info] STORAGE: btrfs [/] @ 16 GB | cifs [/storage] @ 398 GB | fuse.shfs [/config] @ 1.9 TB | btrfs [/watch] @ 16 GB | btrfs [/output] @ 16 GB Note that there is a "cifs [/storage]" item mounted now. I am also using the MKVToolNix docker which works flawlessly on fresh restarts and also uses CIFS mounts. Is this a strange bug or am I missing something?
-
The WireGuard VPN, under Settings -> VPN Manager does not autostart on reboot, even with the AUTOSTART toggle on. It can be manually started by clicking the INACTIVE/ACTIVE toggle and all works fine afterwards. VPN configured as IPv4 + IPv6 with all default settings, except for the local endpoint and port, which are custom. 2 peers setup with "Remote tunneled access" and everything else default. The peers connect and can connect normally once the VPN is activated manually. Tried to delete the old tunnel and create a new one from scratch, but to no avail. All subsequent reboots result in the VPN not starting automatically. All was working fine with the previous release. diagnostics-20220621-2225.zip
-
I'm also having issues when enabling VLANs on my Unraid setup. I have 2 VLANS on my network: 192.168.1.0/24 (LAN) 192.168.2.0/24 (IoT VLAN) I have WireGuard setup as a "Remote tunneled access". When I DON'T have VLANs setup on Unraid, my WireGuard peers can connect to the internet and connect to anything on both the LAN / IoT VLAN. ex. WG peer > 192.168.1.X OK WG peer > 192.168.3.X OK When I DO have VLANs setup on Unraid, my WireGuard peers can connect to the internet but can only access the LAN. Anything on the IoT VLAN has no response. ex. WG peer > 192.168.1.X OK WG peer > 192.168.3.X NO ACCESS Is this a bug in the WireGuard plugin?
-
I wasn’t able to disable SSL - I can access via HTTPS which throws certificate errors. Also the default admin/adminadmin credentials aren’t working… anyone find a workaround for this?
-
bearattack joined the community
-
Hi, I'm trying to setup a remote tunneled access server using IPv4 + IPv6 and a local DNS (pihole) server. I run through the advanced configuration and my clients are successfully tunneling through IPv4, but it seems there is no IPv6 access through the tunnel. Is this a bug or am I misconfiguring something? My config is almost all default settings: