Did you recently change your site from http to https?
What error(s) do you see in the browser console when you’re on that page?
Thank you for responding.
The issue appears on the cPanel toolkit security, when i click fix everything back normal; below what was fixed it, not sure which one.
1- WordPress uses security keys (AUTH_KEY, SECURE_AUTH_KEY, LOGGED_IN_KEY, and NONCE_KEY) to ensure better encryption of the information stored in the user’s cookies. A good security key should be long (60 characters or longer), random and complex. The security check should verify that the security keys are set up and that they contain at least alphabetic and numeric characters.
2- If access permissions for files and directories are not secure enough, these files can be accessed by hackers and used to compromise your website. This security measure sets the permissions for the wp-config file to 600, for other files to 644, and for directories to 755.
These setting set by Wordfence security plugin also maybe.
Appreciate you respond
I don’t use cPanel and note that it’s not part of WordPress. If it breaks WP, then don’t enable that feature! It’s wrong about how files should be secured. 644/755 should be acceptable if your host is properly set up.
You are right, i am confusing about it why we need 600.
Hello Steven,
I got the same issue on another website; the Wordfence plugin is causing this; here is how I fixed it:
1- Rescan the site for security on Toolkit
2- Disable script concatenation for the WordPress admin panel ( security measures should be applied). So when the green checkmark is activated for this option, the backend is back to normal.
Just for info, this could help someone else in future.
Have a great weekend.
