If you visit one of the following endpoints, Coral will return the version you're running and the hash for the latest commit.
/api/v1(works for 4.x.x versions)
/api/version(works for 5.x.x versions)
- Make sure you've adding the correct domains to your Permitted Domains
- Make sure you've correctly added the embed via your CMS to your article pages
- Check the console for any errors and you can file a bug via support if you can't resolve the issue
- If this seems to be isolated to one commenter, it could be related to 3rd party cookies
- Post 4.x Talk doesn't require 3rd party cookies to be enabled. Check the version of Talk you're using and you might consider upgrading.
- A quick fix in the meantime is to ask them to allow 3rd party cookies
- You could also try asking them to clear their browser cache
This depends greatly on what version of Coral you are using and which authentication strategies you've enabled. Some things to check are:
- If using SSO, ensure that your JWT token settings, especially expiry, is being set correctly. You can troubleshoot JWT related issues with the JWT Debugger.
- See if you can isolate if it's a particular group of users that are experiencing this issue, e.g., mods, admins, subscribers? Confirm they have the appropriate permissions to comment.
- Note if this is a new issue that happened after an upgrade - did you read the release notes and confirm that any required manual or automatic database migrations run?
- If a user has been locked out due to too many failed login attempts, the user will have to wait 10 minutes before they will be allowed to login
- Coral does not support changing a User's
user.id. If you attempt to pass an SSO token with a new
user.idbut an existing
user.emailaddress, Coral will throw a
DUPLICATE_USERerror. To correct this, you need to "detach" the user's email address from their original
user.idby sending an API request to Coral's
updateUserEmailmutation, and set the
user.emailfor the original
user.idto some other value. After that you will be able to pass an SSO token with the new
user.emailcombination. The user will lose access to their existing comment history, because according to Coral, they are a new and different user.
- If you're still experiencing issues, log a support ticket so we can help diagnose the issue
Make sure you've enabled the option for “Coral Admin” under the "Configure" -> "Authentication" -> “Login with Single Sign On“ settings. This box must be checked to allow users with the MODERATOR or ADMIN roles to access the Moderation/Admin interface using the MODERATE button.