Cosmetic WARN[0000] spam from WG_PASSWORD_HASH being read as compose variables
Posted by bkjimena11
Running an update (immich, but probably any module update) throws a wall of these: WARN[0000] The "SQfCUrtq" variable is not set. Defaulting to a blank string. WARN[0000] The "jcaQwqESB5eWNBVTwhgOn0" variable is not set. Defaulting to a blank string. Tracked it down — my .env has WGPASSWORDHASH set to a bcrypt hash, and bcrypt hashes are full of $ characters. Docker Compose reads $ in .env values as the start of a variable reference, so it's trying to substitute chunks of my own password hash as env var names. Repeats once per line for every container in the stack. Everything still comes up healthy — seems purely cosmetic, not affecting the actual update or wg-easy auth. But probably worth quoting/escaping WGPASSWORDHASH in the compose file (or however it's referenced) so it doesn't spam warnings like this on every up/update. Install root: /opt/sparkbox Modules enabled: backup, core, dashboard, files, immich, media, pihole, tailscale, vpn
1 replies
Chris wrote:
You've got this spot on — nothing's broken, and both your VPN panel login and the update itself are working fine. What's happening is your saved VPN panel password has some special characters in it, and the updater misreads those and prints the harmless "variable not set" lines you're seeing. Tom already directed a fix so fresh setups store that password the safe way. For your box, SSH in and run this once: sudo sparkbox up That quietly rewrites the saved value the right way, and the warnings should stop on future updates. Thanks for the really clear write-up — you basically diagnosed it for us.