Troubleshooting

Portal is not loading over HTTPS - Ensure the reverse proxy terminates TLS and forwards to the webapp. - Mixed content errors usually mean a redirect from HTTP; check X‑Forwarded‑Proto headers.

Login returns 401 - Confirm mail/SSO configuration and that the API container can reach SMTP. - Check API logs for auth‑related messages.

Migrations fail - Verify DB connectivity and credentials (PCLUE_DB_PW). - Re‑run: docker compose exec api alembic upgrade head.

API container unhealthy during version upgrade - During migration to a new version, the API container may become unhealthy because the migration takes longer than the healthcheck timeout. - Open the logs with docker logs -tf api and wait until the migration runs through successfully. - Afterwards, run docker compose up -d again to start containers that depend on the API container (these were not started initially because the API was marked unhealthy).

Slow UI or search - Allocate more RAM/CPU to Elasticsearch. - Check ES health and index sizes.

Where to get help - Review container logs. - Check the RestAPI health API endpoint for more information. - Check the Changelog for recent changes.