Troubleshooting

Troubleshooting method

1. Identify scope

   Determine which page, service, customer or integration is affected.

2. Reproduce safely

   Confirm the symptom without introducing additional mutation.

3. Check application logs

   Look for the first relevant application error.

4. Check service logs

   Review Nginx, PHP-FPM, database and related service logs.

5. Verify dependencies

   Test database and external provider connectivity.

6. Check recent changes

   Review updates, configuration changes and deployments.

7. Repair narrowly

   Modify only the layer shown to be responsible.

8. Validate

   Repeat the original workflow after the fix.

Blank page or HTTP 500

• Check PHP-FPM service state.
• Review Nginx error logs.
• Review application/PHP error logs.
• Validate PHP syntax for recently changed files.
• Confirm database connectivity.
• Check runtime directory permissions.

Provider connection failure

• Verify the API endpoint and port.
• Confirm DNS resolution and network reachability.
• Verify provider credentials and permissions.
• Check TLS requirements.
• Use the module's connection test where available.
• Review the provider's API response rather than assuming authentication is the only cause.

Notification not received

• Confirm the application created or queued the notification.
• Verify the configured recipient and sender identities.
• Trace the message through the local MTA or relay.
• Check DNS/MX records for hosted mail.
• Review spam filtering or temporary SMTP responses.
• Confirm final mailbox delivery rather than relying only on application-level submission success.

Before escalating

• Record the JKPanel Pro version.
• Record the affected route or operation.
• Capture the exact error message.
• Capture relevant log lines without exposing passwords, API keys or private tokens.
• State the last known working condition and recent changes.