-
Notifications
You must be signed in to change notification settings - Fork 514
Troubleshooting
George Dawoud edited this page Oct 20, 2025
·
8 revisions
Check Your Logs First! Many issues can be self-diagnosed by examining ChurchCRM logs:
- Admin Users: Navigate to Admin → System Logs in the ChurchCRM web interface to view, filter, and manage logs
-
Server Access: Logs are stored in the
logs/directory where you deployed ChurchCRM (e.g.,/var/www/vhosts/churchcrm/logs/) - See the Logging and Diagnostics guide for detailed information on accessing and interpreting logs
We encourage all problems with installations and upgrades to be tracked in GitHub issues. This allows us to document both the problem, and the solution.
If you're encountering difficulties, there's a good chance someone else has had the same issue. Please take a look at issues in these categories to see if your situation has been addressed:
- Installation Guide ← Start here!
- First Run Setup
- Features Overview
Day-to-day usage of ChurchCRM
- User Documentation
- People Management
- Groups & Events
- Tools
- Finances
Server management & configuration
- User Management
- System Maintenance
- Configuration
- Troubleshooting
- Localization
Contributing to ChurchCRM
- Quick Start
- Testing & CI/CD
- Code & Architecture
- Localization
- Release & Security