Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your Dashboard, try deactivating all plugins. If you don’t have access to your Dashboard, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.
If that does not resolve the issue, try switching to the Twenty Nineteen theme to rule-out a theme-specific issue. If you don’t have access to your Dashboard, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.
If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files.
If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that specific time period. If you don’t have access to your server error log, ask your hosting provider to look for you.
Thread Starter
bpjs
(@bpjs)
Hi James,
I’ve tried all of the above – I’ve renamed all of the plugins one by one, reloading the page to see if it will give me access, but none of them do. I’ve renamed every one of the directories for themes the same as above, but not making any difference either. I’ve located the .htaccess file and changed it’s name, reloaded the page, but still cannot get access.
Not sure where I’d find a server error log?
Thank you
The location of the server error log varies greatly depending on your hosting provider and server configuration.
You’ll need to check your hosting provider’s documentation or contact their support for specifics.
Thread Starter
bpjs
(@bpjs)
I’ve done a search for ‘error’ and found:
/tmp/errors
/public_html/error_log
/public_html/wp-admin/error_log
/public_html/wp-content/plugins/error_log
…will it be in one of these?
Thread Starter
bpjs
(@bpjs)
The hosting is done through Hostgator if that helps?
Thread Starter
bpjs
(@bpjs)
[Wed Feb 27 17:59:54 2019] [error] [client 108.179.232.106] SoftException in Application.cpp:313: File “/home1/bpjs/public_html/wp-cron.php” is writeable by group, referer: http://freemoov.co.uk/wp-cron.php?doing_wp_cron=1551311994.2578690052032470703125
[Wed Feb 27 17:58:46 2019] [error] [client 2.25.133.176] SoftException in Application.cpp:313: File “/home1/bpjs/public_html/wp-login.php” is writeable by group
[Wed Feb 27 17:58:46 2019] [error] [client 108.179.232.106] SoftException in Application.cpp:313: File “/home1/bpjs/public_html/wp-cron.php” is writeable by group, referer: http://freemoov.co.uk/wp-cron.php?doing_wp_cron=1551311925.9419739246368408203125
[Wed Feb 27 17:58:41 2019] [error] [client 2.25.133.176] File does not exist: /home1/bpjs/public_html/wp-admin.php
[Wed Feb 27 17:56:35 2019] [error] [client 2.25.133.176] SoftException in Application.cpp:313: File “/home1/bpjs/public_html/wp-login.php” is writeable by group
[Wed Feb 27 17:56:25 2019] [error] [client 2.25.133.176] SoftException in Application.cpp:313: File “/home1/bpjs/public_html/wp-login.php” is writeable by group
[Wed Feb 27 17:56:14 2019] [error] [client 2.25.133.176] SoftException in Application.cpp:313: File “/home1/bpjs/public_html/wp-login.php” is writeable by group
[Wed Feb 27 17:55:56 2019] [error] [client 2.25.133.176] SoftException in Application.cpp:313: File “/home1/bpjs/public_html/wp-login.php” is writeable by group
[Wed Feb 27 17:55:50 2019] [error] [client 108.179.232.106] SoftException in Application.cpp:313: File “/home1/bpjs/public_html/wp-cron.php” is writeable by group, referer: http://freemoov.co.uk/wp-cron.php?doing_wp_cron=1551311750.4109458923339843750000
[Wed Feb 27 17:55:34 2019] [error] [client 2.25.133.176] SoftException in Application.cpp:313: File “/home1/bpjs/public_html/wp-login.php” is writeable by group
[Wed Feb 27 17:54:58 2019] [error] [client 2.25.133.176] SoftException in Application.cpp:313: File “/home1/bpjs/public_html/wp-login.php” is writeable by group
[Wed Feb 27 17:54:50 2019] [error] [client 108.179.232.106] SoftException in Application.cpp:313: File “/home1/bpjs/public_html/wp-cron.php” is writeable by group, referer: http://freemoov.co.uk/wp-cron.php?doing_wp_cron=1551311690.0929439067840576171875
Thread Starter
bpjs
(@bpjs)
I just pulled this from the Hostgator error log section, if it helps.
Seems to be a file ownership problem. If you get in touch with your hosting provider’s support, they’ll be able to clear that up for you.
Thread Starter
bpjs
(@bpjs)
Weirdly, I just changed the permissions for the wp-login file, and turned off ‘write’ for group, user and world – and managed to log-in for the first time. However, now that I’m in, it doesn’t let me make any updates to the plug-ins or update to WordPress 5.1 – it is giving me constant 500 errors… any thoughts?
Thread Starter
bpjs
(@bpjs)
James – you’re a star. I’ve just contacted Hostgator, and they said there were indeed errors with the Files and Folders permissions, which they’ve changed their end, and now that I’ve left the Write permissions off under the wp-login.php file, I can get full access, make changes, etc. as before. Thank you so much!
I had a malware infection on the site, could you recommend a good Plugin to stop this happening?
Carefully follow this guide. When you’re done, you may want to implement some (if not all) of the recommended security measures and start backing up your site.
There are a few different free security plugins that can help you with hardening your WordPress installation. From what I’ve seen, most people use either the Sucuri plugin or Wordfence plugin, but be sure not to use a combination of different security plugins as it can often times lead to them conflicting.
I would recommend installing one of those plugins and configuring any type of server side scanning (sometimes called file integrity) as that will notify you of changes such as file permissions or any other modifications.
Also, if you have multiple domains hosted on your HostGator cPanel user then there is a high chance those websites have also become infected. HostGator usually disables your website once they detect or get reports of malware so it’s best to get these issues resolved before that can happen.
Someone Help Please: I cannot access my wp-admin page in the 2019 theme. I edited the header and then deleted what I had entered, and now I cannot access the login page, Dashboard, etc. I can visit the site but cannot update it at all. Please advise.
@srivers58 Try going to /wp-login.php instead of /wp-admin
I just tried and it redirects to my home page.
I installed a plugin for users to register also.
