PanelConfig
Documentation / Troubleshooting / Troubleshooting common PanelConfig issues

Troubleshooting common PanelConfig issues

A practical checklist for jobs that look stuck, DNS or SSL that has not applied, and email or login problems.

Most issues in a queue-driven panel come down to one question: has the background worker processed the job yet? This guide walks the common cases.

An action looks stuck

Panel and CLI actions that touch the server (provisioning, DNS apply, SSL issuance, backups, service control) are queued as jobs. If something has not taken effect, check the queue first:

php cli/pc jobs:run-next
php cli/pc health

If health reports pending jobs and the worker is not running on a schedule, the jobs simply have not been drained yet.

DNS changes have not applied

Editing a zone bumps its serial and queues a dns.apply job. Confirm the job ran, then allow for normal DNS propagation before testing resolvers.

An SSL certificate did not issue

SSL issuance is queued as ssl.issue. Make sure the domain resolves to this server first — ACME validation cannot complete until DNS points at the right place.

Email is not flowing

Check that the mailbox is active in PCUser, and that the domain's MX and SPF records exist in the DNS editor. Deliverability problems are usually DNS, not the mailbox.

Cannot sign in

Repeated failures are rate limited by design. Wait for the window to reset, then confirm the account is active under PCAdmin → Users. Every attempt is recorded under Audit & logins.

When in doubt, the audit log and login history in PCAdmin show exactly what happened and when.