AI won't connect at all on the Backer level. 7 Media Apps won't start in Media Centre. Been thirty minutes now. Ugreen NAS.
9 replies
tomspark wrote:
Thanks for posting! I see you're hitting fresh-install issues on your UGREEN. Two things are failing (Tom AI + the Media Center stack), which usually points to a DNS, port conflict, or initial app-startup timing issue. Quick first step: open your SparkBox dashboard → Apps → click the Media Center stack and check if the apps show 'healthy' or have error messages. Can you paste one error? Also grab: docker ps output and we'll dig in. This one's on our radar.
hotdogtown wrote:
I got it sorted. It was an issue with Nord. I fixed it with Surfshark. I still cant connect to AI on Sparkbox and the beta. Any thoughts?
tomspark wrote:
Glad the media apps are sorted — and good call on the VPN swap. For the AI, let's pin down what it's actually doing: open Tom AI, send a test message, and paste the exact error you see here (even 'it just spins forever' is useful). Since you just changed VPNs, give the box one full restart first — the AI's connection sometimes needs that after a VPN change. And when you say the beta won't connect either, what do you see there? Paste both and I'll dig in.
hotdogtown wrote:
Sure thing. Classic: Why won't Prowler open after a restart? I hit a problem reaching the AI service mid-task: AI Troubleshooting is temporarily unavailable. Wait a minute and try again.. Try again in a moment. Beta: Why won't Immich open? I hit a problem reaching the AI service mid-task: AI Troubleshooting is temporarily unavailable. Wait a minute and try again.. Try again in a moment.
tomspark wrote:
Perfect, that's exactly what I needed. That 'AI Troubleshooting is temporarily unavailable' message means your box is having trouble reaching the AI service — that's on our side to dig into, not something you broke, especially since Classic and Beta both show the exact same thing. I've logged it and we're on it. One quick thing so I can check your exact build: run sparkbox status in a terminal and paste the version line at the top here. I'll follow up as soon as we've got it sorted.
hotdogtown wrote:
Weird as docker ps access is denied: "permission denied while trying to connect to the docker API at unix:///var/run/docker.sock"
tomspark wrote:
That's the docker group permission issue — very common and totally fixable. Your user needs docker access. Run this once: sudo usermod -aG docker $USER, then restart your terminal or log out and back in. After that, sparkbox status should work without needing sudo. The version line it shows is what we need to debug the AI connection issue. Let me know what it reports and we'll dig in.
hotdogtown wrote:
SparkBox v1.6.358
tomspark wrote:
Perfect, thanks — that's the very latest build, so nothing on your end is out of date and there's nothing more you need to do. The AI issue is confirmed on our side and we're digging into it now. I'll post here as soon as it's fixed so you know when to try Tom AI again. Thanks for sticking with the back-and-forth, it made this easy to pin down.