a66a1b1c33
* Initial plan * Add documentation about KiCad self-signed certificate issues Co-authored-by: jbtronics <5410681+jbtronics@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jbtronics <5410681+jbtronics@users.noreply.github.com>
2.5 KiB
| layout | title |
|---|---|
| default | Troubleshooting |
Troubleshooting
Sometimes things go wrong and Part-DB shows an error message. This page should help you to solve the problem.
Error messages
When a common, easily fixable error occurs (like a non-up-to-date database), Part-DB will show you some short instructions on how to fix the problem. If you have a problem that is not listed here, please open an issue on GitHub.
General procedure
If you encounter an error, try the following steps:
- Clear the cache of Part-DB with the console command:
php bin/console cache:clear
- Check if the database needs an update (and perform it when needed) with the console command:
php bin/console doctrine:migrations:migrate
If this does not help, please open an issue on GitHub.
Search for a user and reset the password
You can list all users with the following command: php bin/console partdb:users:list
To reset the password of a user you can use the following
command: php bin/console partdb:users:set-password [username]
Error logs
Detailed error logs can be found in the var/log directory.
When Part-DB is installed directly, the errors are written to the var/log/prod.log file.
When Part-DB is installed with Docker, the errors are written directly to the console output.
You can see the logs with the following command, when you are in the folder with the docker-compose.yml file
docker-compose logs -f
Please include the error logs in your issue on GitHub, if you open an issue.
KiCad Integration Issues
"API responded with error code: 0: Unknown"
If you get this error when trying to connect KiCad to Part-DB, it is most likely caused by KiCad not trusting your SSL/TLS certificate.
Cause: KiCad does not trust self-signed SSL/TLS certificates.
Solutions:
- Use HTTP instead of HTTPS for the
root_urlin your KiCad library configuration (only recommended for local networks) - Use a certificate from a trusted Certificate Authority (CA) like Let's Encrypt
- Add your self-signed certificate to the system's trusted certificate store on the computer running KiCad (the exact steps depend on your operating system)
For more information about KiCad integration, see the EDA / KiCad integration documentation.
Report Issue
If an error occurs, or you found a bug, please open an issue on GitHub.