Skip to content
Quetz
Open Quetz

Reference

Troubleshooting

Most of these are the app behaving correctly in a way that is easy to misread.

Messaging#

That address has no XMTP inbox yet

The recipient has never signed in to an XMTP client, so there is no inbox to deliver to. Send them your Quetz link. One signature on their side creates the inbox and opens the conversation.

My messages are gone after clearing site data

The local database and its key were cleared together. Sign in again and history re-syncs from the network. Nothing was lost on the protocol side.

A conversation is missing

Check the Requests folder. An unaccepted sender stays there rather than in your inbox. The sync button in the sidebar also forces a full network sync if a device has been offline.

The site updated but the app looks old

Quetz is a single-page app, so a tab left open keeps running the JavaScript it loaded. Hard refresh with Ctrl + Shift + R.

Signing in#

Signature declined

Nothing happens until you approve it, and it is safe to retry. It is a message signature, not a transaction, so it costs nothing and moves nothing.

I switched wallets and my inbox changed

Expected. The inbox is the address, so a different account is a different inbox. Quetz closes the old one as soon as the connected account changes. Switch back and your conversations return.

Wrong network

Messaging does not depend on the connected chain, so this never blocks a conversation. It only matters for on-chain reads such as $QUETZ balances. Use the switch button in the header when it appears.

Rooms#

I cannot post in a gated room

Your balance has dropped below the room’s requirement, or the balance read failed. A failed read is deliberately treated as zero. Re-check with the button in the notice once the balance is back.

The gate option is missing

Room gating turns on when $QUETZ launches. Until then rooms work normally, they just cannot require a balance. See Rooms and $QUETZ.

Still stuck#

  • Try a different browser profile, which rules out extension interference and stale local data in one step.
  • Open the browser console. XMTP surfaces detailed errors there.
  • Reach the team on X.