Hi, just installed Sparkbox. I am pleased with it so far. However, I am getting the error message that container sb-gluetun is unhealthy. Is there any way that I can just go back and fix the information required for the Wireguard stuff regarding my VPN. I am sure that is where the error is occurring. I am using Surfshark for which I already had an account. As soon as I get this glitch fixed I will be more than happy to subscribe to the box. I really am quite impressed by the box and the apps that are available. One other question, I can't get Portainer to open is that because of the forementioned gluetun error? Thanks!
15 replies
Chris wrote:
This is usually just a VPN detail that needs re-entering, not something broken. In the dashboard go to Settings → Network → Edit VPN settings. For Surfshark, the WireGuard private key is one 44-character line ending in = — log into Surfshark → VPN → Manual setup → Router → WireGuard → Generate a new key pair, and copy just the Private key into the WireGuard private key field. Put the Address from that same Surfshark page in the WireGuard addresses field (Surfshark's is usually 10.14.0.2/16). Save, and the tunnel should turn healthy within a minute or two. Portainer is separate from the VPN, so gluetun isn't what's blocking it. Open it from its tile in the dashboard (or http://your-box-ip:9000) and log in as admin with the password SparkBox generated for you at install.
homeserver_76 wrote:
Hello Chris. I have attempted to follow the directions that you gave me above to input and verify setting for the VPN. It is still crashing. I even downloaded the configurations script, deleted all entries and then uploaded the script to the server. It will restart, but then crashes out. Would it be appropriate for me to upload my log file for the VPN? I am pretty sure it does not contain my private key for Surfshark. I don't know why it keeps crashing. I have 16 of my 17 apps working properly. The one that is 17th, the VPN is the only one not working. Please let me know if it is safe to upload my VPN log file. Also still can't get my http://your-box-ip:9000) and log in as admin with the password SparkBox generated for you at install to work. Thanks for your help again. Also, I will delete the existing key pair and will create a new one. And try again. Donald
Chris wrote:
Checking the log is the right idea — just don't paste the whole thing here, since a VPN log can carry your private key and we don't want that public. Run and share only the last line that shows an error; that'll tell us exactly why it's crashing. On Portainer: was a placeholder — swap in your box's real IP. Easiest is , which prints the Portainer link with the correct port (it isn't always 9000). Log in as with the password SparkBox generated. And yes, regenerating the Surfshark key is the right call — just keep the private key as the full 44-character line ending in , with the address .
Chris wrote:
Sorry — my last message got mangled and the commands vanished. Here they are cleanly: To see why the VPN is crashing, run: sudo sparkbox logs gluetun — then share just the last error line (not the whole log, since it can contain your private key). For Portainer, your-box-ip was just a placeholder. Run: sparkbox urls — it prints the real Portainer address with the correct port. Log in as admin with the password SparkBox generated for you. And yes, regenerating the Surfshark key is right — private key is the full 44-character line ending in =, address is 10.14.0.2/16.
homeserver_76 wrote:
Chris: Thanks for being so understanding and patient with me. I have everything up and running. I got the problem with Gluetun taken care of. All files/containers are running and marked as healthy. I will follow the guides from here on in to try to see what happens now that it's running. One thing I would appreciate is if you can tell me how would I get to a terminal window for the Linux subsystem to issue commands and queries such as port numbers themselves. I do not know how to run SparkBox URLs. Sorry for my newbie questions. But believe me I am learning a lot from this experience. I do have computer experience from many years ago even at my late 70s age:)
Chris wrote:
Wonderful news, Donald — having every container healthy is exactly where we want you. You mostly will not need the terminal: the dashboard is point-and-click, and each app tile opens it right up. When you do want the full list with port numbers, open the Windows Start menu, type Ubuntu (or whichever Linux you installed), and click it — that is the Linux subsystem terminal. Then type: sparkbox urls and press Enter. It prints every app with its address and port, and any SparkBox command runs there the same way.
homeserver_76 wrote:
Chris, I was having too many issues with trying to run SparkBox on Windows. In particular, a lot of the services were not seen on my local lan. So I created an external plug in ssd with Ubuntu on it (this is the same Ryzen 9 mini-computer that I was running windows 11 on). That is working very well. Unfortunately, I didn't follow the guide for creating what logins were to go first out of the arr stacks. So while the services are running my connection to the portals are not allowing me in (with the ones that are requiring the user names and passwords). For example I can't use Portainer, nor Seerr. So my question is this. Can I just reinstall the packages for say media, and start that part over again? Or do I have to wipe out everything else i.e. nuke the whole server and begin again. I am enjoying trial and error; but I know I should and will be following the written guides. I am asking this because I did add some other services such as Adguard and that is working well. I am certain that all of my arr apps are up and running wihout issues. I just can't get into some of them because the password issues. And please I wanted to tell you that I will be paying for the Sparkbox.....because of its ease and the time and effort that you and Tom have put into this project. Regards! Donald
Chris wrote:
Donald, you don't need to reinstall or nuke anything — both of these are simple password resets, and neither touches your data or your other services. For Portainer, run: sudo sparkbox repair-portainer — it regenerates a fresh admin password and saves it for you, then log in as admin with that new password. For Seerr, there is no separate Seerr account — it signs you in with your Jellyfin login. Run: sudo sparkbox reset-password jellyfin — it prints a brand-new password, and that same password opens Seerr too. That's genuinely all it takes. And thank you for the kind words about the project — it means a lot, and Tom will be glad to hear it.
homeserver_76 wrote:
Chris, I have a question for you. I am using an MacMini M4 (Apple Silicon). Is there anyway that I can use my Mac and dedicate docker and all Sparkbox files to an external drive? I do not have enough free storage space on my internal storage. Thanks for advising me on this.
Chris wrote:
Good question — and the honest answer is SparkBox itself runs on Linux, not macOS, so it won't install directly on the Mac Mini. On an Apple Silicon Mac the supported route is a Linux virtual machine: install a free one like UTM, put an Ubuntu VM inside it, and give that VM its disk on your external drive — that's where Docker and all the SparkBox files live, so it solves the storage problem too. Then install SparkBox inside the Ubuntu VM exactly like the VPS guide shows.
homeserver_76 wrote:
Thank you Chris. I actually got it working under windows. However, I am finding it difficult to locate answers in the Sparkbox documentation. For instance, now the only problem I am having is that evidently my api key for Qbittorrent was incorrect. I got a new one; but when I check the documentation for anything relative to editing the .env file, there is nothing there regarding that subject. I think that it would/should be there. I hope that doesn't mean that i didn't have VPN protection? So now I have no instructions as to where the .env file is located. I know how to edit it using nano but not how to get to the file.
Chris wrote:
When you reported that Gluetun and the containers were healthy, the VPN tunnel itself was up; a qBittorrent credential issue does not turn VPN protection off. On your Windows install, open Ubuntu/WSL and run sudo nano /opt/sparkbox/.env to open SparkBox’s settings file. Change only the specific setting a guide names, and do not paste the file or its values here because it can contain passwords and keys. For the qBittorrent issue, reply with the setting name or exact error only, with any values redacted, and I’ll verify the supported correction.
Anthony wrote:
Hi homeserver76 — checking in on the qBittorrent setting. Were you able to identify the setting name or the current error? Please share only that name or redacted error text, never the key or your settings file, and I will verify the next step. — Anthony, AI Senior Support
homeserver_76 wrote:
Yes, thanks! Everything is up and running well.
Chris wrote:
Great to hear it's working.