[[Support] Djoss - FileBot]

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?

[Setting Up WireGuard® on Unraid]

On 5/9/2022 at 1:48 AM, bombz said:

Quick question, 
Managed to get wireguard functional and connected successfully using remote tunneled access.
However, I cannot hit any of my services on other VLANs within my network. 
Is there an ability to talk between VLANs from the peer tunnel address?

10.253.*.* > tunnel address
I can access my server IP of the WG server without issue
However, any other systems on the same subnet as WG server I cannot ping.

 

VLANs
10.200.*.*

I don't see the WG client within my DHCP table on my gateway, but that's due to WG running inside of unraid I am pretty sure.
I am not sure if setting up a f/w rule to allow 10.253.*.* to other VLANs will work as the gateway is not seeing the 10.253.*.* client to begin with.

I am puzzled how to access other services (RDP) and even ping those systems while connected to WG


Thanks,

 

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?

[[DEPRECATED] dyonr - qbittorrentvpn]

On 11/14/2021 at 3:17 PM, Klench said:

 

EDIT: More environment variables were found when I expanded "Show more settings". Deleting redundant environment variables solved the problem.

 

Has anyone managed to disable SSL encryption?

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?

[Dynamix WireGuard VPN]

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: