has issued multiple warnings over “slow MySQL queries” or something like that. Today, I got a new warning over cpu usage. The host has shut my site down again for the second time.
Yeah, I find that highly suspect. Unless your are being purposefully DDOSed via registrations, you shouldn’t be over-using any resources, and for that matter the host should be able to identify if it was a DDOS attack. It really might be time to just switch hosting providers.
Another issue I have (maybe not related) is that, after the site was moved and set up again, I could not access my dash board features. I got an error 500.
Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins. 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 Fourteen theme to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via FTP or SFTP, 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 FTP or SFTP and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your FTP or SFTP 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 time period. If you don’t have access to your server error log, ask your hosting provider to look for you.
This site was set up to be a community site similar to twitter, but with a slightly different flair. Right now, it has become a nightmare.
Ah, that’s important to know. If you expect to be near the size of Twitter, you do need a robust VPS or dedicated server(s), otherwise it will indeed be a nightmare. I hope you aren’t planning to launch something like that on shared hosting.
