A cPanel account can be accessible while the public site fails because the document root, PHP version, database connection, or resource limit changed.
What to check
- Review the relevant error logs
- Confirm the document root and PHP version
- Check database credentials and resource limits
What the results mean
Compare the account logs with the error shown in the browser. If the server is responding but the application is failing, changing DNS is unlikely to help.
Find which layer failed
A cPanel login working does not mean the public website is healthy. Check whether the domain reaches the account, whether the document root contains the expected files, and whether the application can reach its database. A blank page or server error needs the relevant PHP and web server logs before making changes to permissions or software versions.
Protect the account before changing PHP
Write down the current PHP version and active extensions, then back up the site and database. A version switch can expose outdated code or plugin incompatibilities. Test the specific failing page, form, and admin area after each change. Resource warnings should be compared with actual usage rather than solved by repeatedly raising limits.
Should I reinstall the website?
Reinstallation is rarely the first diagnostic step. It can overwrite configuration and content while leaving a database or domain problem untouched. Preserve the existing files and use the recorded errors to identify what actually needs repair.
Greg Grigorian
For hosting trouble, migrations, backups, or a site that stopped working, get a clear diagnosis and a tested recovery path. Greg can review the setup and handle the work.