tomspark wrote:
You didn't break anything — that 'VPN dropped, downloads paused' banner is actually SparkBox's kill switch doing its job: it blocks all download traffic until the VPN is safely connected, so nothing ever leaks. So the only thing to fix is getting Proton to connect. The VPN's own log tells us exactly why it won't. Over SSH, run this and paste what it shows: sudo docker logs sb-gluetun --tail 30 The most common Proton snag is the WireGuard details — Proton needs you to use a WireGuard config (a private key generated in your Proton account's WireGuard section), not the OpenVPN username/password. The log will confirm which it is. Paste it here and I'll point you to the exact fix.
tomspark wrote:
Those screenshots actually solved it — thank you. Your terminal shows SparkBox is running inside a Proxmox LXC container (the 'Ubuntu LXC Container' line at the top). That's the whole problem: an LXC container can't build a VPN tunnel by default, so Proton can never connect — and that's why every media app keeps restarting (they all wait for the VPN). The empty 'docker logs sb-gluetun' fits too: gluetun can't start without that tunnel device. This is a Proxmox gotcha, not a SparkBox one — definitely not your fault. Two ways forward: 1) Easiest, and what I'd recommend: reinstall SparkBox in a full VM instead of a container. In Proxmox, create a VM (not an LXC), put Ubuntu on it, and run the install there — the VPN then just works. Another user hit this exact thing and a VM fixed it right away. 2) Keep the LXC (advanced): you'd add TUN device access to the container's config on the Proxmox host. Doable but fiddly — happy to walk you through the exact lines if you'd rather not rebuild. Which way do you want to go?