Zero

I recently changed from PIA to Mullvad using this guide. But the Webgui does not work anymore. This is a rundown of my settings: Priviliged container Extra parameters: --sysctl="net.ipv4.conf.all.src_valid_mark=1 VPN enabled vpn username/password default VPN_PROV = custom VPN_CLIENT = wireguard No strict portforward Lan network = 192.168.178.0/24 (server ip is 192.168.178.x) Name servers = default I let Sabnzbd run, drag my wireguard config in there and rename it to wg0.conf. The container starts without any error and sabnzbd also has no errors in the log. What am I doing wrong here? I tried different container tags, different settings, different WIreguard configs but nothing helps. I saw some threads where people had the same problem but they did not post a fix (like this one). I think I found it. I'm using Tailscale subnet router to connect to my machines so therefore I am not in the LAN network I have defined. I need to find out what IP my container is seeing when I cannot to it so I can add it to the LAN network. final edit: I fixed it by adding 100.64.0.0/10 (found the cidr here) to the lan_network variable

Wondering the same, if I find a solution for this I can really replace my Pi.

That's what I do too, but where do you enter the names for the Pi to resolve? I want to type: http://banana in my browser and be forwarded to the 192.168.1.100 IP. What file should I edit to make this possible?

I want to use my Pi-Hole as local DNS resolver, but want to keep my current DHCP server (so not using PiHole DHCP). What would be the best way to do this?

People who get the 403 error and you have an USG Gateway, SSH into the gateway and enter this command: configure set service dns forwarding options rebind-domain-ok=/unraid.net/ Whoever added all the useful 'Help' information, you're amazing!

I just did that, but it's still giving errors

Thanks for the tip! Tried setting the memory to one and two percent, hope it helps! If it crashes again, I will get the diagnostics and see what's up

My unRaid WebUI gets unresponsive every two days or so, SMB and all the dockers are still reachable but the UI is stuck. After quite some Googling there isn't really an option to only restart the webui and not the whole machine/array. I'm now reading into cpu pinning and I hope that will fix it but maybe you guys have some other ideas/tips?

Just digged through the syslog a bit, seems like nobody SSHD into it, can't find anything weird in the logs either.

Yeah that is a good idea, a mistake to be learned from

Long story short, wanted to open port 80 for another machine and accidently entered my unRAID ip (it was a long day). So my unRAID box was open to the internet without any verification (was a fresh install and just set it up) for about 10~ hours, any tips for damage control and seeing if anyone messed with my server? I would be open to a fresh install but I'd like to keep my dockers + files on my disk

Do you might have an idea why the plugins don't work for me 99% of the time? Whenever I reboot the plugins are disabled again and I have to re-enable them

I just downloaded and setup deluge, but whenever I enable any plugins (e.g. label or extractor) they are reset after boot. I want to use this with sonarr but even tho I enabled the label plugin, sonarr and radarr say I don't

Since the last update my Sonarr has been acting realllyyy weird, the RSS sync and scanning library are taking ages and here are the logs I didn't change and of the settings, just added some shows. It's not like Sonarr is not working but it's realllyy slow and glitches pretty hard.

I'm not saying CA is the problem but I'm just trying to determine where I exactly fucked up. If I want to be sure I don't have any previous files of the docker are left, what directories should I make sure I've deleted? (e.g. dockerman, appdata etc.)