JohnDoughDump

That fixed it for me! Thank you!

Hi, A couple of days ago, my container started failing even if I didn't change anything from a configuration point of you (the container has been updated but I didn't change anything). My container has been working without any issues for more than a year now and rolling back to a previous version doesn't seem to change anything. I'm running this container in Truenas scale which I'm aware isn't unraid but they should work in a similar fashion anyway. Were there any changes in the variables or configuration? Now the container won't start and I get this error: 2025-06-24 15:58:27.176268+00:00[info] Attempting to bring WireGuard interface 'up'... 2025-06-24 15:58:27.176288+00:002025-06-24T15:58:27.176288823Z 2025-06-24 15:58:27.176802+00:002025-06-24 11:58:27,176 DEBG 'start-script' stderr output: 2025-06-24 15:58:27.176842+00:00error: Found argument 'wg-quick' which wasn't expected, or isn't valid in this context 2025-06-24 15:58:27.176847+00:002025-06-24T15:58:27.176847716Z 2025-06-24 15:58:27.176851+00:00USAGE: 2025-06-24 15:58:27.176900+00:00boringtun-cli [OPTIONS] <INTERFACE_NAME> 2025-06-24 15:58:27.176907+00:002025-06-24T15:58:27.176907735Z 2025-06-24 15:58:27.176928+00:00For more information try --help 2025-06-24 15:58:27.176932+00:002025-06-24T15:58:27.176932277Z 2025-06-24 15:58:27.176936+00:002025-06-24 11:58:27,176 DEBG 'start-script' stdout output: 2025-06-24 15:58:27.176961+00:00[warn] Failed to bring 'up' WireGuard userspace implementation 'boringtun-cli' 2025-06-24 15:58:27.176979+00:002025-06-24T15:58:27.176979823ZAny idea what could cause that? I'm using Wireguard with Mullvad. Thank you for the help!