Troubleshooting: where to look first

Troubleshooting

Most problems announce their cause in a log. Reproduce precisely, read the logs, then change the smallest thing.

SymptomLook at
Access deniedThe role's permissions, then whether the session is stale.
Blank or critical-error pageThe PHP and web-server logs, file permissions, OPcache after a deploy.
Paid but invoice unpaidBilling › Gateway Log, then the Module Log.
Email not arrivingUtilities › Logs › Email Log, then SPF, DKIM and DMARC.
Nothing recurring happenedLast Automation Run, the cron command and the PHP version cron uses.
Broken pictureThe file's address, case-sensitive path and where the library says it is used.

Never debug by exposing secrets

Remove passwords, keys, session ids, license keys and customer data from anything you paste into a ticket or a screenshot.

Full guide

The complete reference is Troubleshooting in the WBAMS documentation.

  • 0 Users Found This Useful
  • troubleshooting, errors, logs
Was this answer helpful?

Powered by WBAMS