Skip to main content

AI connection problems

Aivie keeps track of every call it makes to the AI model, for two profiles: Chat, which writes text, and Image, which draws images. When a profile has a problem, a notice appears at the top of every Aivie screen. This page explains the notice and what to do about each cause. The status of both profiles is on the Subscription screen, see AI connection.

You see "AI is temporarily unavailable"​

The notice reads AI is temporarily unavailable. Your administrator has been notified. It does not say why.

Cause​

The last call with the chat profile failed, or the last call with the image profile failed within the past 24 hours. Only members of Aivie-admin see the cause, because it is usually something only an administrator can fix. See Who sees what.

An image problem is only part of the notice for 24 hours after the last failed call. The chat profile counts for as long as its status is Problem.

Fix​

  1. Tell a member of Aivie-admin. They see the cause in the notice, as described below.
  2. After the cause is fixed, the notice goes away by itself. Aivie reads the status again about once a minute, so allow a minute and move to another screen.

The notice also goes away when the next call works, or when an administrator presses Test connection and it succeeds. See The notice does not go away after the fix.

The notice shows a line about the cause​

Members of Aivie-admin see one line per profile with a problem, and a button Open the Subscription screen.

Cause​

The sentence depends on the cause. Aivie works out the cause from the answer of the provider. Below, OpenAI stands for the name of your provider.

Fix​

Find your line in the sections below and follow the fix of that section.

The API key for OpenAI no longer works​

The line reads The API key for OpenAI no longer works. Check and replace the key in the settings of OpenAI.

Cause​

The provider refused the key (HTTP status 401 or 403, or an answer that says the key is invalid). The key was revoked, was typed wrongly, or is no longer readable by your site. After a move to another server, see API key unreadable after a move.

Fix​

  1. Create or copy a working key in your OpenAI account.
  2. Enter it in the field OpenAI secret key of the setup wizard, press Set up Aivie, and restart the site when the wizard asks for it.
  3. Press Test connection.

The credit at OpenAI has run out​

The line reads The credit at OpenAI has run out. Top up at the provider; Aivie then works again by itself.

Cause​

The prepaid balance at your AI provider is empty. This is the balance of your own provider account, not something inside Aivie. The provider answered with HTTP status 402, or with a message about a credit balance or quota.

Fix​

Add credit to your account at the provider. Aivie needs no action: the status turns back to OK at the next successful call, or press Test connection to see it at once.

The spending limit at OpenAI has been reached​

The line reads The spending limit set at OpenAI has been reached. Raise the limit at the provider; Aivie then works again by itself.

Cause​

A spending limit that you set at the provider, for the organisation or for the project, has been reached.

Fix​

Raise the limit in the settings of your provider account, or wait until the limit resets at the provider. Then press Test connection.

The provider is limiting the number of requests​

The line reads OpenAI is limiting the number of requests right now. This usually resolves itself; try again shortly.

Cause​

The provider answered with HTTP status 429: it received too many requests in a short time.

Fix​

Wait a few minutes and press Test connection. If it keeps coming back, check the rate limits of your account at the provider.

The provider cannot be reached​

The line reads OpenAI cannot be reached right now. This is not caused by Aivie; wait and try again later.

Cause​

The provider is down or overloaded (HTTP status 500, 502, 503, 504 or 529).

Fix​

Wait, and check the status page of your provider. The status clears with the next successful call.

The configured model no longer exists​

The line reads The configured model no longer exists at OpenAI. Check the model name in the AI profile.

Cause​

The provider answered with HTTP status 404 for the model of the profile. The model was withdrawn or renamed, or its name was changed in the profile.

Fix​

  1. Open AI → Profiles.
  2. Open the profile that has the problem: the Aivie chat profile (alias aivie-chat) or the Aivie image profile (alias aivie-beeld).
  3. Choose a model that your provider offers, and save.
  4. Press Test connection.

An unknown problem with the connection​

The line reads There is an unknown problem with the connection to OpenAI. See the server logs for details.

Cause​

The call failed in a way Aivie does not recognise, for example a network error, or an answer without a usable status.

Fix​

Look in the Umbraco log. A failed chat call is logged as an error that starts with Call to agent, followed by the agent alias. A failed image call is logged as Image generation failed for, followed by the name of the image. The log line holds the message of the provider. Press Test connection after you have fixed the cause.

The notice does not go away after the fix​

Cause​

The status shows the result of the last call. After you fix the cause, it only changes when the next call works, or when you press Test connection.

Fix​

Members of Aivie-admin find Test connection next to the title AI connection on the Subscription screen. It makes a short call with the chat profile and shows the new status at once. It does not test the image profile, because every image costs money. An image problem therefore stays visible on the Subscription screen until the next image works, but it drops out of the notice after 24 hours.

If there is no chat profile yet, the button shows There is no chat profile 'aivie-chat' yet; there is nothing to test. Run the setup wizard first. Aivie also makes this test call by itself every morning, see Scheduled jobs.