Chapter 28 • Guide 29 of 31
Troubleshooting workflow
When an operation fails:
- Read the complete error shown by Core Panel.
- Check whether the resource is still pending or running.
- Correct the specific prerequisite, such as DNS, a port, credentials, storage capacity, or an invalid value.
- Use Retry when it is available.
- Review the closest diagnostic page: website logs, traffic, cron log, mail diagnosis, mail logs, Nginx logs, ports, service status, or audit log.
- Create or download a backup before a destructive repair.
- Send feedback with a sanitized log or screenshot if the problem appears to be a Core Panel defect.
Common issues
SSL certificate fails: Confirm every selected hostname resolves to this server and that inbound port 80 is reachable.
Upload is rejected: Check the File Manager or feedback file limit. For application uploads, compare PHP upload_max_filesize and post_max_size with the site's Nginx client_max_body_size .
Email cannot send: Verify outbound TCP 25 with Email → Delivery & sync , check PTR and DNS, inspect the queue and mail logs, then run Delivery diagnosis .
DNS changes are not visible: Check zone status, delegation health, record TTL, registrar nameserver settings, and secondary synchronization.
Website is over its limit: Review Access & limits , mailbox and database usage, website files, logs, and available host storage.
Terminal tab is missing: Enable SSH terminal access on the primary site account and confirm the account is active. The assigned access package must also permit Terminal.
CLI inventory is empty: Run sudo core-panel status and compare its counts with the dashboard. The installed CLI automatically loads the protected control-plane configuration. If the dashboard contains resources but every CLI count is zero, run core-panel version and confirm /usr/local/bin/core-panel points to the current Core Panel release. Upgrade or repair the Core Panel installation if the version reports development or the binary points outside /opt/hostpanel/current. Do not expose the database URL while troubleshooting.
Continue this workflow