Troubleshooting

Every Qorum error message, what it means and how to fix it. Start with the connection test: it finds most problems in seconds.

Test the connection

Checks whether the key exists, whether your page's address is allowed and whether your computer's clock is right. To test the login and the webhook, use the dashboard's Test connection tab.

In the widget

The comments don't show up

• It shows "Qorum: missing key or ref". The key or ref option is missing from Qorum.montar, or the data-key/data-ref attribute is empty.
• Nothing shows up. Open the browser console (F12). If there's a "Content Security Policy" error, allow Qorum as explained in Widget. If you see "Qorum is not defined", the widget.js script didn't load before the call.
• It shows "Could not load the comments." The message right after it says why. The most common ones are below.

This page is not allowed for this site

The page's origin isn't on the site's domain list. Remember that with and without www, http and https, and different ports count as different addresses. Test the origin in the form above and check the list in Settings → Allowed domains. See also Domains.

Invalid site key

The public key is wrong, incomplete, or the site was disabled. Copy the key again from the Install tab. It starts with pk_.

Login expired, please log in again

The token sent was refused. The widget keeps working for reading and calls your onExpired. Causes:

• The token is past its exp. Renew it with onExpired, like in the Login example.
• The token was signed with another key: the public key instead of the secret one, or an old secret key after a rotation.
• aud isn't this site's public key, or sub has a character that isn't accepted.
• The site's login is turned off in Settings.

Paste the token in the dashboard's Test connection tab: it lists exactly what's wrong.

The Log in button doesn't show up

It shows up when Qorum accounts are on, when you pass onLogin or when there's a login page configured. With only your site's login on and none of these, the widget has nowhere to send the person.

The comment disappeared after publishing

• If the approval notice showed up, it's in the queue. See Moderation → Pending.
• If it had a blocked word, a link or an image, it may have gone to the queue because of the site's rules.
• If the page uses another ref (for example, with parameters in the address), it's another conversation.

Slow down, wait a few seconds before commenting again

There's a 5-second gap between one comment and the next from the same person, against spam. Moderators don't have this gap. Other limits (per hour, per day, repeated text) are listed in Spam protection.

Too many actions in a row, wait a moment

More than 30 write actions (comment, like, edit...) in one minute by the same person. Wait a minute.

Problems with images

• The Image button doesn't show up: images are turned off in Settings.
• Format not accepted: only JPG, PNG, GIF and WebP. Renamed files (a PDF called .jpg) are refused.
• Image larger than 32 MB: make it smaller before uploading.
• Resolution too large: over 40 megapixels (for example, 8000 by 5000 pixels). Scale it down before uploading.
• The image service did not respond: the upload failed halfway. Try again.
• Invalid image when commenting: through the API, only addresses returned by POST /v1/images for the same person are valid.

On your server

Invalid secret key

The key in X-Qorum-Secret isn't the current one. If someone clicked Rotate secret key, update your server with the new one. Also check that you sent X-Qorum-Key with the public key of the same site.

The webhook doesn't arrive

See When it doesn't arrive on the webhooks page.

Request without the dashboard header

The /painel/api routes belong to the Qorum dashboard only. To automate things, use the management API.

Response codes

Limits