Verity API Connection Failed: Fix 401, 429 & Mod Errors

Fix status 401

A 401 Unauthorized response means authentication failed. Confirm that the selected Verity project supports the provider, create or retrieve the key only in the provider account, enter it through the maintainer-documented local configuration, and send one short test. If the key appeared in a screenshot, log, chat, or repository, revoke it before testing again.

Fix status 429

A 429 Too Many Requests response means the provider limit was reached. Stop rapid retries, open the provider limits page, check request and token limits for the selected model, wait for the reported reset, and retry once. Reinstalling Verity, replacing the JAR, or repeatedly rotating a valid key does not increase the quota.

Route every other failure

If there is no 401 or 429, start with the first failed row and keep the evidence from that layer.

Last successful eventLikely failed layerNext evidence

Game never reaches menuVersion, loader, dependency, JavaFirst meaningful latest.log error

Menu loads; Verity absentWrong profile, pack, world, triggerMod list or active pack list

Verity appears; no textProvider, model, backendExact redacted provider error

Text works; no voiceTTS, narrator, audio device, permissionVoice setting and audio output

Singleplayer works; server failsServer/client parity or server configurationServer log and exact project

Crash before the menu

Match the exact project, Minecraft version, loader, and relations. Verity JE 5.7.4 belongs to Forge 1.20.1; Revamped belongs to NeoForge 1.21.1 and requires GeckoLib. Fabric is not listed for either tracked Java route.

World opens but Verity is absent

Confirm the project is visible in the Java Mods list or the Bedrock packs are active in that world. Use a new disposable world. On Bedrock, verify Beta APIs and the selected project's required behavior/resource packs.

Verity appears but cannot answer

The installation and appearance layers have passed. For Groq, continue to the dedicated setup page. For Ollama, confirm the local service and configured model. For other providers, use only the options documented by the exact Verity project and keep credentials out of logs.

Text works but voice fails

Keep the working AI configuration. Check the project's selected voice backend, Minecraft sound levels, operating-system output device, narrator or TTS availability, microphone permission, and language limitations.

Server crashes or stays silent

Verify the server and every client use the same game version, loader, project release, and dependencies. Then determine where the selected project expects provider configuration. A server catalog listing is not proof of runtime compatibility.

Safe support report

Include project ID, release, Minecraft version, loader/build, dependencies, device or host, failure stage, and the first meaningful redacted error. Exclude API keys, full personal paths, private chat, and world files.

FAQ

Questions

Does reinstalling Verity fix API connection failed?

Usually not. A 401 is an authentication problem and a 429 is a rate-limit problem. Reinstall only when the failure is in the loader, dependency, or project file layer.

What should I remove from a support log?

Remove API keys, tokens, personal paths, private chat, and unrelated personal information while preserving the error and environment fields.