“If your site was in working order in the last week or so, but is no longer available,” continues the documentation, “this would generally fall into one of five categories: ‘Changes to DNS or cache,’ SSL/redirect issues,’ ‘Manual update last week,’ ‘Account limits or suspension,’ or ‘Temporary network outage.’ The easiest solution is simply to track down what specific error message you yourself are seeing. For instance, you may see an “NXDOMAIN error,” meaning you’re seeing a DNS issue. Then again, seeing the message ‘500 Internal Server Error’ ordinarily means you have a faulty PHP script or a mucked up .htaccess file. When presented with a message reading ‘403 Forbidden,’ it generally relates to file or permissions issues, then again, a ‘Suspended’ message simply means you’re indeed suspended’.
Isolating the Connection
Before trying to fix the server, you need to establish whether this is a universal problem or one that is happening on your own system. Checking the page via mobile data or Incognito Mode will help you establish whether this is something to do with stale DNS or whether your service provider is filtering content. Also, please check whether your page is accessible via both the http:// and https:// prefixes of your URL address. Accessible over one but not the other means you have a problem with SSL or a redirect error, while failing on both means looking to what changes have occurred since all was last well, most probably files or changes to nameservers/settings or “Force HTTPS” functionality.
Quick Fixes and Resource Limits
If you want to go back online quickly, there are a few “reset” procedures that must be followed. If it’s a DNS problem, simply switch over to Cloudflare (1.1.1.1) or Google (8.8.8.8) and then issue an ipconfig /flushdns command from computer command line inputs. If WordPress has crashed because of a software update, you would simply update .htaccess or change your “/wp-content/plugins/” folders using an ftp site update by renaming .htaccess or “/wp-content/plugins/”. Final reminders are that if you are using a freeware hosting site and end up hitting a CPU limit or a traffic burst (traffic surge), don’t be alarmed if your site restrictions are tightened unexpectedly in a short period of time. If this takes place and you receive a site “not suspended” warning or if you notice a spike in “503 errors,” be reminded that an ftp site file copy or site file back-up must be accomplished quickly in this situation in case site entry privileges.