Troubleshooting¶
Start with the symptom, then verify the relevant layer without exposing credentials.
Blank page or server error¶
- Check the web-server and PHP error logs.
- Confirm the PHP version meets the requirement.
- Check PHP syntax:
- Verify file permissions and PHP's include path.
- Confirm required extensions are loaded.
Database connection fails¶
Check $dbsys, host, port, database name, username, password, and table prefix.
Confirm the matching PDO driver is installed and test network or socket access
from the application host.
Do not paste production credentials into an issue.
Login fails¶
Determine whether the failure is in session handling or credential verification. Then check:
- the configured
$auth["session"]and$auth["type"]; - identity-provider availability and TLS;
- user filters, roles, groups, or attributes;
- disabled or expired accounts; and
- PHP extensions required by the backend.
Keep a separate recovery procedure for administrator access.
Times are wrong¶
Verify the room's timezone, area timezone, global $timezone, PHP timezone,
and daylight-saving transition. Use the timezone of the rooms, not necessarily
the server or administrator.
Email does not arrive¶
Verify the enabled event and recipient role, then check sender address, backend, SMTP transport, authentication, TLS, and mail-server logs. Test create, change, and delete separately.
A configuration change has no effect¶
Common causes include:
- editing a defaults file instead of
config.inc.php; - changing area defaults when the existing area has database settings;
- editing a different deployment or site in multisite mode;
- PHP opcode caching; and
- a later configuration assignment overriding the earlier one.
Collect useful diagnostics¶
Record the MRBS version, PHP version, database type, relevant extension list, exact error, affected page, and minimal reproduction. Redact credentials, session identifiers, email addresses, and private booking data.