Skip to main content

Concierge Not Working?

Concierge Not Working?

If Concierge isn't responding or shows an error, work through this checklist. Most issues resolve with the first few steps.

Quick Checklist

1. Is QUI Core running?

Concierge is part of QUI Core. If the dashboard loaded, QUI Core is running. If you can't access the dashboard at all, start QUI Core first.

2. Is the central hub reachable?

Concierge fetches its configuration from the central hub. If the hub is down or unreachable, you'll see "Concierge Unavailable."

Check your internet connection. If the hub is temporarily down, wait a few minutes and try again.

3. Are you logged in?

Concierge requires authentication. If your session has expired, you'll get authorization errors.

Fix: Log out and log back in. This refreshes all authentication tokens.

4. Do you have balance?

Every Concierge message uses your account balance. If your balance is zero, Concierge can't generate responses.

Fix: Go to the Billing tab in the sidebar and add funds.

5. Is Concierge enabled?

The platform administrator can disable Concierge globally. If it's disabled, you'll see a message saying "Concierge is currently disabled."

Fix: Contact your administrator to re-enable it.

Common Issues

"Concierge Unavailable" on page load

The dashboard can't fetch Concierge configuration. Usually means the central hub is unreachable.

  • Check your internet connection
  • Wait a few minutes if the hub is temporarily down
  • If QUI Core was just started, give it a moment to establish connections

Messages send but no response appears

Your message was sent but the AI didn't respond. Possible causes:

  • No balance — check the Billing tab
  • Authentication expired — log out and back in
  • Network interruption — the stream was interrupted mid-response

"AI service temporarily unavailable"

A generic error that means something went wrong in the response pipeline. Usually temporary.

  • Try sending the message again
  • If it persists, check the Services tab to see if any services are offline
  • Log out and back in to refresh authentication tokens

Terminal commands fail with "Terminal Service not available"

The Terminal Service (which runs separately from QUI Core) isn't running.

  • Check the Services tab for Terminal Service status
  • Terminal Service needs to be started separately in some configurations

Terminal commands fail with "Command blocked"

The command you're trying to run isn't in your active preset's allowed list.

  • Check your current preset in Terminal Settings (below the chat input)
  • Switch to a preset that includes the command you need (e.g., Developer for docker commands)
  • Or add the specific command to your manual whitelist

Still Not Working?

If none of the above resolves the issue:

  1. Check the Services tab in the dashboard — are all services showing as healthy?
  2. Try refreshing the page (F5)
  3. Try logging out completely and logging back in
  4. If the problem persists, contact your system administrator

Note: Concierge is designed to help you troubleshoot QUI itself — but it can't diagnose its own unavailability. If Concierge is down, use the Services tab and the steps above to investigate manually.

Updated on Mar 21, 2026
QUI