Blurt not working? A step-by-step troubleshooting guide

First determine whether the problem affects one frontend or the entire network. This avoids unnecessary key changes and duplicate transaction submissions.

Posts or communities will not load

1. Refresh and check your internet connection.
2. Open the same public post in another compatible frontend.
3. If only one frontend fails, investigate its server, RPC endpoint or indexing service.
4. If several fail, look for community announcements and retry later.

Images are replaced by filenames

If a post shows IMG_1234.jpeg as text, confirm that its body or metadata contains a complete hosted image URL. Some older uploads depended on servers that no longer respond. A similar filename does not prove it is the correct picture. Image guide →

Your signing extension is not detected

Verify that WhaleVault or another compatible tool is installed, unlocked and permitted on the exact site. Mobile browsers may have different extension support. Use Posting authority for ordinary social actions, not Owner.

My comment is missing after submission

There can be a delay before an indexer shows the new comment. Check another frontend and refresh rather than clicking Submit repeatedly.

A transaction signature fails

Match the requested authority with the operation, confirm available BLURT for fees, check the RPC connection and review the wallet error. Never publish private keys or recovery information in screenshots.

I still see an old design or stale posts

Reload without cache. Offline pages may display previously stored content. Avoid clearing all site data when it may include local drafts or interface settings.

Where can I report the issue?

Include the public URL, browser, approximate time and exact error message, but remove secrets. Ask the community on BlurtForum.