mirror of
https://github.com/wassname/talk.git
synced 2026-08-18 12:30:39 +08:00
4d41d999fb
* added storyURL and storyID * added story scraping section * fixed typo on sso * rebaseing on latest release/4 branch * updated version on slack docs * added Contributing a Translation section to developing * fixing typos * updated v5 config page, reorder list, add toc * added cli sect, fixed contact menu link * updated talk to coral on contact page * added a new v5 auth section * added session length to auth docs * added an admin settings page to v5 * added v5 css section * added a v5 notifications section * updated faq and troubleshooting, moved out of v4 menu * added migrating to v5 and moved migrating section out of v4 * added plugins note to migration pg * fix: linting and extra HTML * change sidebar migrating v5 to v5.0+ Co-Authored-By: Wyatt Johnson <wyattjoh@gmail.com> * downtime being likely is too optimistic, it will be required Co-Authored-By: Wyatt Johnson <wyattjoh@gmail.com> * rewords plugins note on migrating to v5 Co-Authored-By: Wyatt Johnson <wyattjoh@gmail.com> * tag code block as html Co-Authored-By: Wyatt Johnson <wyattjoh@gmail.com> * added link to contributing * rephrased openid connect description * fixed link to contributing * correcting descriptions of email auth behavior Co-Authored-By: Wyatt Johnson <wyattjoh@gmail.com> * Adding link to css classnames Co-Authored-By: Wyatt Johnson <wyattjoh@gmail.com> * renamed new auth to Social and Email Authentication * pulled extra line breaks Co-authored-by: Wyatt Johnson <accounts+github@wyattjoh.ca>
39 lines
2.6 KiB
Markdown
39 lines
2.6 KiB
Markdown
---
|
|
title: Troubleshooting Tips
|
|
permalink: /troubleshooting-tips/
|
|
---
|
|
|
|
## How do I find out what version I'm running?
|
|
|
|
If you visit one of the following endpionts, 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)
|
|
|
|
## I've installed Coral but I can't see the comment stream appear on my articles
|
|
|
|
* 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](mailto:support@coralproject.net) if you can't resolve the issue
|
|
|
|
## My commenters are reporting they can't see the comment stream, but I'm able to
|
|
|
|
* 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
|
|
|
|
|
|
## My commenters are reporting that they cannot login to Coral
|
|
|
|
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 4.x.x, review your `plugins.json` and server logs to ensure your auth plugins are enabled and working correctly. Check [our auth docs](/talk/integrating/authentication/) for more tips.
|
|
* 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](https://jwt.io/).
|
|
* 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](https://github.com/coralproject/talk/releases) and confirm that any required manual or automatic database migrations run?
|
|
* Confirm that users who are affected have the correct `username.status`. If users have status `UNSET`, this is related to a bug with upgrading from 3.x to 4.x that has affected some organizations. Read more here about [upgrading from 3.x to 4.x](/talk/migration/3/).
|
|
* If you're still experiencing issues, log a [support ticket](mailto:support@coralproject.net) so we can help diagnose the issue
|
|
|
|
|
|
If a user has been locked out due to too many failed login attempts:
|
|
* How long does the user have to wait before they will be allowed to login? 10 mins |