Title: Getting 403 errors when I clicked Test Cache button
Last modified: March 9, 2023

---

# Getting 403 errors when I clicked Test Cache button

 *  Resolved [David LeBlanc](https://wordpress.org/support/users/davidtleblanc/)
 * (@davidtleblanc)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/getting-403-errors-when-i-clicked-test-cache-button/)
 * Hello,
 * I am getting the following and not sure what is causing this. I was using WP-
   Fastest Cache and switched to WP-SuperCache because of the a Site Health check
   item could not detect presence of a page cache.
 * I am not at all sure how to fix it.
 * I installed WP-Super-Cache, clicked the Test Cache Button after getting it set
   up and I got the following:
 * Fetching [https://www.mysite.org/](https://www.mysite.org/) to prime cache: **
   OK** ([0.html](https://www.ism-houston.org/wp-content/cache/0.html))
 * Fetching first copy of [https://www.mysite.org/](https://www.mysite.org/): **
   OK** ([1.html](https://www.ism-houston.org/wp-content/cache/1.html))
 * Fetching second copy of [https://www.mysite.org/](https://www.mysite.org/): **
   OK** ([2.html](https://www.ism-houston.org/wp-content/cache/2.html))
    - Page 1: 403 (Forbidden)
    - Page 2: 403 (Forbidden)
 * **The pages do not match! Timestamps differ or were not found!**
 * Things you can do:
    1. Load your homepage in a logged out browser, check the timestamp at the end of
       the html source. Load the page again and compare the timestamp. Caching is working
       if the timestamps match.
    2. Enable logging on the Debug page here. That should help you track down the problem.
    3. You should check Page 1 and Page 2 above for errors. Your local server configuration
       may not allow your website to access itself.
 * I did thing 1 and 2 and have yet to do thing 3. I think that is an issue with
   the hosting company, but before I go to them I want to make sure the issue with
   the site itself.
 * Coincidently, I am also getting this from Site Health
 * **Your site could not complete a loopback request**
 * Loopback requests are used to run scheduled events, and are also used by the 
   built-in editors for themes and plugins to verify code stability.
 * The loopback request returned an unexpected http status code, 403, it was not
   possible to determine if this will prevent features from working as expected.
 * **Unable to detect the presence of page cache**
 * Unable to detect page cache due to possible loopback request problem. Please 
   verify that the loopback request test is passing. Error: Forbidden (Code: http_403)
 * Page cache enhances the speed and performance of your site by saving and serving
   static pages instead of calling for a page every time a user visits.
 * Page cache is detected by looking for an active page cache plugin as well as 
   making three requests to the homepage and looking for one or more of the following
   HTTP client caching response headers:`cache-control`, `expires`, `age`, `last-
   modified`, `etag`, `x-cache-enabled`, `x-cache-disabled`, `x-srcache-store-status`,`
   x-srcache-fetch-status.`
 * I also get this from the Site Health tool
 * **You should use a persistent object cache**
 * The hosting provider does not provide persistent object cache I was told by support.
 * I think they are all related.
 * Thank for any help you can provide.

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Support [Paulina H. (a11n)](https://wordpress.org/support/users/pehaa/)
 * (@pehaa)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/getting-403-errors-when-i-clicked-test-cache-button/#post-16557593)
 * Hey David,
 * The loopback request issues in conjunction with the 403 errors most likely indicate
   that your webserver configuration prevents internal requests. A misconfiguration
   of [BasicAuth](https://href.li/?https://en.wikipedia.org/wiki/Basic_access_authentication)
   is one of the most common ones. I would recommend that you check that with your
   host.
   Other possible reasons could be:
    - Misconfiguration of internal DNS.
    - Coming soon or maintenance mode plugins. Do you have such a plugin activated?
    - Security plugins that blocking internal requests. If you have a security plugin
      active, please deactivate it temporarily and try again.
 * I hope that the above helps.
 *  Thread Starter [David LeBlanc](https://wordpress.org/support/users/davidtleblanc/)
 * (@davidtleblanc)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/getting-403-errors-when-i-clicked-test-cache-button/#post-16558765)
 * Pauline
 * Thanks for the reply. I will go through the list above and report back.
 * No, I do not have a maintenance mode plugin. Any recommendations?
    -  This reply was modified 3 years, 2 months ago by [David LeBlanc](https://wordpress.org/support/users/davidtleblanc/).
 *  Plugin Support [Alin (a11n)](https://wordpress.org/support/users/alinclamba/)
 * (@alinclamba)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/getting-403-errors-when-i-clicked-test-cache-button/#post-16569124)
 * Hi David,
 * > No, I do not have a maintenance mode plugin. Any recommendations?
 * We apologize for any confusion. Our intention was to inquire whether you are 
   using a maintenance plugin on your site and whether disabling it temporarily 
   could help troubleshoot the Jetpack connection issue. Maintenance plugins can
   sometimes interfere with Jetpack and we wanted to explore all possible causes.
 * > Thanks for the reply. I will go through the list above and report back.
 * Great, sounds good! Looking forward to hearing back from you!
 *  Plugin Support [Stef (a11n)](https://wordpress.org/support/users/erania-pinnera/)
 * (@erania-pinnera)
 * [3 years, 2 months ago](https://wordpress.org/support/topic/getting-403-errors-when-i-clicked-test-cache-button/#post-16596966)
 * Hello [@davidtleblanc](https://wordpress.org/support/users/davidtleblanc/),
 * Do you have any updates for us? We usually close any non-active threads after
   one week, so before marking this as solved we’d like to know how’s going there
   🙂 Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Getting 403 errors when I clicked Test Cache button’ is closed to new
replies.

 * ![](https://ps.w.org/wp-super-cache/assets/icon-256x256.png?rev=3506220)
 * [WP Super Cache](https://wordpress.org/plugins/wp-super-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-super-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-super-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-super-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-super-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-super-cache/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [Stef (a11n)](https://wordpress.org/support/users/erania-pinnera/)
 * Last activity: [3 years, 2 months ago](https://wordpress.org/support/topic/getting-403-errors-when-i-clicked-test-cache-button/#post-16596966)
 * Status: resolved