Understanding Wistia Errors in Hurree

If you're experiencing issues with your Wistia widgets, this guide explains the most common errors and how to resolve them. Each error below matches the message you'll see in Hurree.

If you encounter an error that isn't covered below, please contact our support team for assistance.

Explanation: Hurree was unable to verify your Wistia connection. This usually happens when your authorisation has expired, your password has been changed, or access to Hurree has been revoked from within your Wistia account.

How to solve: Reconnect your Wistia account through Hurree to restore access. Once reconnected, your widgets will begin updating again from the next scheduled sync.

Explanation: You don't have permission to access this Wistia resource. This can occur if your user role has changed, access has been revoked, or you have not been granted the appropriate level of access within your Wistia account.

How to solve: Check that your Wistia account has the necessary access rights, or contact your administrator and ask them to review your permissions. Once the required access has been granted, refresh your connection and try retrieving the data again.

Explanation: The requested Wistia resource could not be found. This may occur if a video, project, or channel has been deleted or moved within Wistia, or if the reference is incorrect.

How to solve: Review the relevant Wistia account and verify that the resource still exists. If it has been removed, you may need to update your widget settings or select an alternative data source.

Explanation: The request took too long to complete, so Wistia stopped waiting for a response. This can happen during periods of slow connectivity or heavy load, or when a large volume of video data is requested at once.

How to solve: Check your connection and try again. If timeouts keep recurring, consider narrowing the date range on your widget to reduce the amount of data being retrieved, and please contact our support team if the issue persists.

Explanation: The data sent with this request did not pass validation, meaning Wistia could not process it as expected.

How to solve: Check that all fields in your integration settings are correctly filled in and try again. If the issue persists, please contact our support team.

Explanation: Wistia restricts the number of requests allowed within a given time window, and if your connected widgets are pulling data at a high frequency, this limit may occasionally be reached.

How to solve: Wait a moment before trying again; your access will resume automatically once the rate limit window resets. If you are consistently hitting this limit, please contact our support team so we can review your connector configuration.

Explanation: An unexpected error occurred on Wistia's servers. This is not caused by any action on your part, and as the issue originates within Wistia's infrastructure, it is outside of our control.

How to solve: Internal server errors are typically temporary and often resolve automatically. Wait a moment and try again, or check your widget after the next scheduled sync period. If the error persists after multiple sync attempts, please contact our support team for assistance.

Explanation: You may occasionally see 400: Bad Request. This indicates that one or more elements of the request sent to Wistia were invalid or incorrectly formatted; it is typically handled automatically and is rarely caused by anything on your side.

How to solve: Review your integration settings for any incorrect entries and try again. If the error persists, please contact our support team, and we'll investigate.

If you've completed the troubleshooting steps above and are still experiencing issues with your Wistia widgets, our support team is here to help. Share the error message you're seeing along with any relevant details, and we'll work with you to identify and resolve the issue as quickly as possible.