NotABanana

You mean it's not possible with your container, no way to interface with SteamCMD? Because you can use 2FA with steamcmd. If it's just a limitation of the container, is it possible to maybe sign in on desktop and transfer some kind of token file? Got the mod issue sorted though, zomboid has separate entries for mods and workshop items, has to be entered in both

Im using the zomboid server, and for some reason it's refusing to load some mods, so Im trying to log in to steam and let that download my workshop files since transferring my .vcf/the mod folders isnt working, how can I sign in with 2fa? I assume I need to enter steam guard code into steamcmd but Im not sure how to interact with steamcmd from the console?

Is that not the proper way to add a bigger drive when a data drive fails? Here from google, one of my data drives has failed, and my replacement is bigger than parity. Is the procedure not parity swap current parity to new bigger drive, then rebuild data onto the old parity drive from the new parity drive?

That's for a VM, how do you pass it through to a docker container? The UI only has dropdowns for VMs

Sorry edited my post without seeing you had replied. The issue was my wg0.conf from Mullvad was still present in the appdata. Unfortunately I deleted it without looking so can't tell you what went wrong with the file, but that resolved the issue, it connected and handled the port all fine automatically after that.

What is the correct way to setup PIA with port forwarding? I was previously using a wireguard config for Mullvad, and swapped VPN_PROV from custom to pia, then entered my user/pass, and started it up. Currently it gets stuck on "[info] Trying to connect to the PIA WireGuard API on 'xx.xx.xx.xx'...". Will post logs if needed/this is something that needs troubleshooting but Im figuring Im just missing some step of the setup. Edit: nevermind me, deleting the wg0.conf fixed the issue. It seems swapping from custom to pia doesn't remove the old one, and that's what my issue was. Leaving up in case someone finds it via search in the future

There's no way it's a software issue? I also had the same error pop up after using unbalance, and these are brand new drives with less than 1000 powered on hours.

How can you write/delete files with root level permission then?

1. 192.168.4.26 2. Bridge, the default. I see what I've done wrong now, thanks! For anyone else reading this if your router uses anything other than 192.168.1.x, make sure you set "lan network" correctly.

I had this issue previously with deluge and now I've migrated to qbittorrent and having the same issue. I am using mullvad vpn via wireguard with a wg0.conf file. It is successfully connecting to the VPN but the webui is unavailable. With the VPN disabled webui works fine. supervisor.log

I'm fairly new to using unraid and docker so this may be user error, but I set this up with mullvad, and cannot access the webui, it just times out. The webui works if I disable the VPN, and the VPN is otherwise working (Checked via console)