Next on Understanding Errors:
Next on Understanding Errors:
Bluesky Widget Errors and Troubleshooting Guide
If you encounter an issue with your Bluesky widgets, don't worry, most errors are uncommon and can be resolved quickly. Below, you'll find explanations for the most common Bluesky widget errors and the recommended steps to fix them. If you're experiencing an error that isn't listed here, please contact our support team for further assistance.
Something Went Wrong on Bluesky's End
Explanation: Occasionally, Bluesky may experience temporary service disruptions or AT Protocol API-related issues that can affect third-party integrations and widgets. As these issues originate within Bluesky's platform, they are outside of our control.
To resolve this, we recommend waiting a few minutes before trying again. Temporary outages are often resolved automatically by Bluesky. If the issue persists for an extended period, please contact our support team and we'll investigate further.
Resource Not Found
Explanation: The content you're trying to access through your Bluesky widget is no longer available. This can happen if a post has been deleted, removed, or if the associated account has been deactivated or changed its handle.
How to resolve this: Check the relevant Bluesky account and verify that the post, profile, or content source still exists and is publicly accessible. Note that Bluesky handles (e.g. @yourname.bsky.social) can be changed by users, if an account has updated its handle since you connected the widget, the original reference may no longer resolve correctly. If the content has been removed or the handle has changed, you'll need to reconnect the integration using the updated account details or select an alternative source for your widget.
You Do Not Have Permission to Access This Resource
Explanation: Your account does not have the required permissions to access the selected Bluesky resource. This can occur if the connected Bluesky account has been set to a restricted visibility, if your app password has expired or been revoked, or if the account owner has changed their privacy settings since the integration was first connected.
How to resolve this: Check that the Bluesky account connected to Hurree is still active and set to the correct visibility. Bluesky uses app passwords rather than your main account password for third-party integration, if the app password used during setup has been revoked or regenerated, you will need to create a new one in your Bluesky account settings (Settings → Privacy and Security → App Passwords) and reconnect the integration in Hurree. If the account belongs to another user or your organisation, contact the account administrator to confirm the app password is still valid and that the appropriate access has been granted.
Handle or Account Not Recognised
Explanation: Hurree is unable to locate the Bluesky account associated with your widget. This typically occurs when a Bluesky user has changed their handle, migrated their account to a different Personal Data Server (PDS), or when a custom domain handle has been misconfigured or has expired.
How to resolve this: Verify that the Bluesky handle entered during setup is current and correct. If the account owner has migrated to a self-hosted PDS or changed their custom domain handle, you will need to update the account details in your Hurree connector settings to reflect the new handle. If you are using a custom domain as your Bluesky handle (e.g. @yourbrand.com), ensure that the domain's DNS records are still correctly configured to point to the Bluesky network.
⚠️ Note: This article is intended only for Hurree users troubleshooting Bluesky Widget errors within the Hurree platform. If you're seeing Bluesky errors outside of Hurree, please visit the X Help Center.