Strapi errors show up in two places: the API responses your site receives (with a status code and an error name), and Strapi's server output, which has the full error. Start with the server output. One specific trap is documented by Strapi: if you changed the admin panel's URL but not its cookie path, logging in "succeeds" and then dumps you back on the login page with no error.
What's the problem
Your site can't load content from Strapi (API errors such as 401, 403, 404 or 500), the admin panel won't load or won't let you log in, or Strapi won't start.
Why it happens
- Permissions: the public or authenticated role isn't allowed to read that content type (403).
- Wrong API token or an expired one (401).
- A server error in a custom controller, service or lifecycle hook (500).
- Admin URL and cookie path mismatch, causing a login loop.
- Config changes that need the admin panel rebuilt.
- Database connection problems, so Strapi won't start.
How to fix it
- Read Strapi's server output for the full error at the time of the failure.
- For 403s, check the role permissions for that content type.
- For 401s, check the API token your site sends.
- For admin login loops, make sure the admin
urlandauth.cookie.pathmatch. - After changing server or admin config, rebuild the admin panel.
- If Strapi won't start, check the database settings and that the database is running.
What Preventionlabs checks
One click runs the full report on your domain. For this problem it shows whether your site loads, how fast, and where its redirects go; up to 50 pages from your sitemap, listing any that fail or are slow, plus broken links on them. With Cloudflare connected, it also shows recent deploys and account changes, with their times. It has no connection to your CMS itself, so check the CMS's status page and API settings too.
Run your free reportYour first report is free, no card needed. Then A$50 a month, up to 10 domains. Read-only: it never changes anything.
Sources
- Strapi: Admin panel configurationofficial docs
When you change url , also set auth.cookie.path to the same value. Otherwise the admin panel cannot read its own authentication cookie: the login request succeeds, every request after it is rejected, and the panel returns to the login page with no error.
- MDN Web Docs: 500 Internal Server Errorreference
The HTTP 500 Internal Server Error server error response status code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.
Preventionlabs is independent and not affiliated with Strapi. Product names are used only to describe the problem.
← All of Headless CMS