Hi guys! 

My website went offline the day before yesterday. It displayed a HTTP500 code. I have had this a few times every since starting my website and it was always fixed very quickly. Now though, 2 minutes after it is fixed it goes offline again. Over and over and over again. I honestly have no idea what is going on, where I can go to have it fixed and what can be done to save my website. It's a travel blog and I have worked so hard on it. I feel ill thinking about losing years of work and content. 

Ahoy. Might be worth checking any plugins or htaccess? See https://www.elegantthemes.com/blog/tips-tricks/how-to-fix-the-500-internal-server-error-on-your-wordpress-website.

Edited June 19, 20206 yr by Jo 90
Removed direct link

Backed up website and downloaded it, wordpress is completely reinstalled from scratch. Still the same problem

Could well be a problem with your wp_config.

You need to make sure the DB credentials match.

500 errors can stem from a few things:

.htaccess errors

Try disabling it and run your URL's through index.php, e.g. www.example.com/index.php/some-page
If the problen clears up your htaccess is most likely at fault

Server not configured properly for your CMS

Are you missing and required libraries?
Are the PHP and MySQL versions running on the server correct for your CMS

Is your server overloaded?

Cheap/budget web hosts put too many sites on each server, resulting in all site competing for resources, can cause 500 errors.

Old/dodgy CMS addons

3rd party CMS addons can cause numerous problems, make sure they are updated and remove any you're not using. One solution is to disable all addons, if the site works perfectly add them back one at a time till it breaks, that may point to the culprit.

Code errors

It's possible some poor code can cause 500 errors when front end templates are called. What I normally do for these is strip out a template to the basics, then reapply bits of code until an error happens, again that helps debug anythjing that's at fault.

And lastly, turn on your CMS's debugging tools if it has them, that can often give some hints as to what may be the cause.