What debugging information do we need to assist you?
Last updated: October 2, 2025
Common debugging information
When assisting you with your Strapi project, we may require some information from you to assist you and provide the best support possible. Here is a list of common needs that we may ask for:
Brief description of the issue
Steps to reproduce
Expected Behavior
Strapi Version (exact like 5.10.4)
Alternatively you can just provide your project's
package.json
Any logs (server backend and/or browser console/network logs)
Self-hosted Enterprise & Growth information
For self hosted customers we may need the following additional information:
Your hosting environment (Provider and resource types e.g. AWS EC2, AWS, RDS, AWS ECS, etc.)
Include as much details as you can such as instance sizes, database type, version, region, and availability zone
In some cases we may need a copy of your project's code-base for local reproduction
Optionally providing a database dump from a development or staging environment where you can reproduce the issue would be helpful
Strapi Cloud information
For Strapi Cloud customers we may need the following additional information:
Your regional location compared to the Strapi instance
Your application's project and debug name
Screenshots of the runtime logs when you encounter the error as our ability to review logs older than a few hours is limited
Browser/Network logs for the Strapi Cloud dashboard if you cannot load things like the runtime logs or other frontend errors
If you experience loading issues with logs (such as persistent loading spinners or infinite loading), try these troubleshooting steps:
Open the runtime logs page in an incognito/private browser window
Disable browser extensions temporarily, particularly development tools like Vue.js devtools, React devtools, or similar extensions that may interfere with the dashboard's functionality
Important limitation for data transfers: When using the Data Transfer Service (DTS) to transfer data from local to Strapi Cloud, note that Admin Users, API Tokens, and Transfer Tokens are NOT transferred for security reasons. If you cannot login after a transfer, you'll need to use the original admin user account that was created when the Cloud project was first deployed, or create new admin users manually in the Cloud instance.