Post by account_disabled on Dec 24, 2023 1:21:57 GMT -3
If not, change the plugin folder from the previous step back to its original name. Move on to the next plugin, repeating the previous steps. This process may take a little time if you have many plugins, but it is essential to test each plugin one at a time. If, at some point, you identify the plugin generating the error, you can uninstall it or replace it with another tool. If you get to the end of these steps without finding a solution, you can move on to the next step. 2. Deactivate the Website Theme Now that you've ruled out your plugins as possible causes of the 503 error, it's time to do the same with your active theme. In fact, even the theme could create compatibility problems. Unfortunately, the procedure is not the same as above.
If you use CDN , a quick way to figure out if this is causing the problem is to Buy Bulk SMS Service temporarily disable it. Every CDN should include some features that allow you to suspend its services. If you're on Kinsta, you can disable your Kinsta CDN by navigating to CDN → “Disable CDN” in your MyKinsta dashboard : Enable/disable CDN option in MyKinsta Enable/disable CDN option in MyKinsta The procedure you need to follow may be different depending on the CDN you use. Cloudflare has sometimes been known to cause 503 errors. If you can't find a way to pause it, search your service's knowledge base, which usually has detailed instructions. If you don't use a CDN, or find that suspending service doesn't help, there are still other solutions to try.
Remember to reactivate the CDN before continuing. 4. Restrict the WordPress 'Heartbeat' API The WordPress Heartbeat is a native WordPress API that is used to automatically save content, show you plugin notifications, let you know when someone else is working on a post you're trying to access, and more. Just like a normal heartbeat, the API works in the background with a high frequency, so you don't miss anything. As you can imagine, this API consumes server resources. This is usually not a problem, but it can lead to a 503 error if your server can't handle the load. The quickest way to determine if the Heartbeat API is at the center of your problems is to temporarily disable it.
If you use CDN , a quick way to figure out if this is causing the problem is to Buy Bulk SMS Service temporarily disable it. Every CDN should include some features that allow you to suspend its services. If you're on Kinsta, you can disable your Kinsta CDN by navigating to CDN → “Disable CDN” in your MyKinsta dashboard : Enable/disable CDN option in MyKinsta Enable/disable CDN option in MyKinsta The procedure you need to follow may be different depending on the CDN you use. Cloudflare has sometimes been known to cause 503 errors. If you can't find a way to pause it, search your service's knowledge base, which usually has detailed instructions. If you don't use a CDN, or find that suspending service doesn't help, there are still other solutions to try.
Remember to reactivate the CDN before continuing. 4. Restrict the WordPress 'Heartbeat' API The WordPress Heartbeat is a native WordPress API that is used to automatically save content, show you plugin notifications, let you know when someone else is working on a post you're trying to access, and more. Just like a normal heartbeat, the API works in the background with a high frequency, so you don't miss anything. As you can imagine, this API consumes server resources. This is usually not a problem, but it can lead to a 503 error if your server can't handle the load. The quickest way to determine if the Heartbeat API is at the center of your problems is to temporarily disable it.