Restoring the backup appeared to help restart MySQL, which appears to have been experiencing problems. Nevertheless, database inconsistencies may still exist in Magento. Try these actions:
Look for the error log that corresponds to your record number in Magento's var/report/ folder.
If you have access to the CLI, run bin/magento setup:upgrade and bin/magento cache:flush.
Make sure the right database credentials are in env.php in app/etc/.
Your database is operational because phpMyAdmin is functioning, but Magento may require a database reindex or missing tables. Tell us what the error log contains! paybyplatema
MySQL seemed to have been having trouble restarting, however it seemed to be resolved by restoring the backup. However, Magento may still have database inconsistencies. Try these steps:
Search the var/report/ folder in Magento for the error log that matches your record number.
Run bin/magento cache:flush and bin/magento setup:upgrade if you have access to the CLI.
Verify that env.php in app/etc/ contains the correct database credentials.
Because phpMyAdmin is working, your database is operational; however, Magento might need a database reindex or tables that are missing. Tell us what's in the error log!
Run Magento commands from the command line to refresh everything.
Use these steps
Clean the cache
Redeploy static content
Flush the cache
Also check file permissions and ownership.
This usually fixes the issue when changes or styles are not showing.