This is becomming a long time. My question: So glad the AI working after the update SparkBox AI replied: I hit a problem reaching the AI service mid-task: AI Troubleshooting is temporarily unavailable. Your box itself is fine — everything in your dashboard (apps, logs, updates) keeps working while we sort this out. Try me again in a minute; if it keeps repeating, contact support. (code U502). Try again in a moment. What I still need help with: (describe what didn't work or what's still broken)
8 replies
Chris wrote:
I’m glad the AI is working again after the update, and I’m sorry this took so long. Is the original issue you were troubleshooting fixed now too? If not, please reply with what is still going wrong and your SparkBox version, and we’ll pick it up from there.
hotdogtown wrote:
The AI is definitely not working. I hit a problem reaching the AI service mid-task: AI Troubleshooting is temporarily unavailable. Your box itself is fine — everything in your dashboard (apps, logs, updates) keeps working while we sort this out. Try me again in a minute; if it keeps repeating, contact support. (code U502).
hotdogtown wrote:
Immich is still down from our chat two weeks ago. I was hoping AI could fix it.
Chris wrote:
Sorry, hotdogtown. You've been stuck on this far too long, and part of that is on us: on your earlier Immich thread we told you the database was corrupted and couldn't be saved. That was wrong. What actually happened: Immich's database stopped accepting Immich's saved password. There's a repair command for exactly that, but the way it checked the password let it through without really testing it. So it told you the password "matches its database" and changed nothing, while the database kept turning Immich away. SparkBox 1.6.808, out now, fixes that check. The one thing to run (the repair saves a safety copy of the Immich database before it changes anything): sudo sparkbox upgrade sudo sparkbox repair-immich-db-auth It should finish with "Immich's database login is repaired and the app is healthy." If it prints anything else, paste the last few lines here. You don't need Tom AI for this one. About Tom AI: that U502 is on our side, not your box, and trying again in a minute won't clear it for you. I've passed your box's case to the team to trace. We've also corrected what our support assistant knows about this, so the next person whose Immich password stops matching gets the repair and isn't told their database is gone.
hotdogtown wrote:
Can you let me know when this support assistant will respond? Its been over one month. I don't want to leave sparkbox or leave negative reviews. I think it's been great, but apart from one week, this AI hasn't worked so I wonder why I have paid.
Chris wrote:
I’m sorry we left you waiting, and that my earlier reply sent you back to the Immich repair as if its “password matches” result meant the app was fixed. That check can stop before refreshing Immich, so please don’t repeat it; we’ve corrected what I know about that failure so I don’t send the next person down the same path. I’m Chris, and Anthony and I are Tom’s support team; Tom is the CEO and doesn’t work the support queue himself. I’m picking this up here now. For the billing concern, please open a private ticket at https://demox.world/support and Anthony will take care of it. For the Immich issue, what SparkBox version is installed?
hotdogtown wrote:
I dont care about Immich. I want the AI sorted.
Chris wrote:
Understood, the AI is what matters here, and I found why it kept failing for you. Tom AI sends each question to an AI provider, and since September 17 that provider has been refusing requests that come from your region. Our service had no second route for that case, so every question you asked ended in the "temporarily unavailable (code U502)" message. That was on our side, not your box, and retrying could never have fixed it. As of a few minutes ago, when that refusal happens your question goes to our other AI provider instead. There is nothing to update or restart on your box. Please open Tom AI and ask it anything. If you still see an error, reply here with the code it shows and I'll pick it straight up. Sorry it took this long to track down.