Support » Fixing WordPress » Suspicious comments flagged as spam just as site starts serving Internal Server

  • In my 13 years of WordPress, I’ve never seen anything like this. About an hour ago I was alerted by one of my users that the website was displaying an Internal Server Error 500 message on every page. I consulted my host’s tech support, and they were unable to determine the cause. I then noticed that I had about 20 comments in the moderation queue, all of which are very suspicious (see screenshot). I have no idea what to do. The website will load intermittently but it is very slow. I’m not sure what’s going on, and I have no idea what to do. Any help would be greatly appreciated.

    Here’s a screenshot of the comments: https://imgur.com/MfnnmYk

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator t-p

    (@t-p)

    Online scan by Sucury failed: https://sitecheck.sucuri.net/results/https/www.coaster101.com

    I suggest contacting your host and find out what’s going on.

    Thread Starter VSRJ

    (@vsrj)

    Unfortunately the host wasn’t able to pinpoint the problem and told me they would follow up within 24-48 hours…

    Moderator t-p

    (@t-p)

    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 (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 default theme for your version of WordPress to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, 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 time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.