In short. MyKinsta password protection cannot be enabled while Kinsta CDN or Edge Caching is enabled.
Definition: MyKinsta password protection is Kinsta's
.htpasswdtool for requiring authentication before visitors access a WordPress site. Kinsta's configuration documentation states that the tool cannot be enabled while Kinsta CDN or Edge Caching is enabled.
Key facts
- Kinsta places password protection in a site's Tools section. The setup asks for a username and password, then enables the protection across the site. Kinsta's configuration documentation describes this workflow.
- Kinsta documents the conflict with both CDN and Edge Caching: password protection cannot be enabled while either setting is enabled. The Kinsta CDN documentation repeats the same constraint.
- The password guide says the
.htpasswdtool protects the entire WordPress site and is available for live sites and staging environments. Kinsta's htpasswd documentation gives that scope. - Kinsta describes Edge Caching as storing a site's cache in Cloudflare's global network, with cached responses delivered from a nearby location. The Edge Caching documentation explains that model.
What exactly is unavailable?
The restriction applies to the MyKinsta password protection tool. Kinsta's configuration page, last updated July 1, 2025, tells you to open the site's Tools section, click Enable, and choose a username and password. The same page states that the WordPress site requires authentication after the feature is enabled, and that credentials can later be changed or the feature disabled.
The password guide identifies the mechanism as basic HTTP authentication. It says the tool creates a hidden file in the site's Nginx configuration that stores the encrypted username and password. This is site-wide protection: the guide describes the entire WordPress site and includes both live sites and staging environments in its scope.
The rule is a documented product constraint. Kinsta does not give a deeper technical reason for the incompatibility on these pages.
Why do CDN and Edge Caching matter here?
Kinsta CDN and Edge Caching are separate caching settings, and the password restriction names both. The CDN page, last updated May 28, 2026, says Kinsta's CDN is powered by a Cloudflare integration and is enabled by default on new sites. When enabled, Kinsta serves static content such as images, CSS, and JavaScript files through its Content Delivery Network.
The Edge Caching page describes a different cache scope. It says Edge Caching saves the Kinsta site or page cache from the site's data center to Cloudflare's global network of 300+ data centers. It also states that cached responses are delivered from the location closest to the visitor and that the cache expires every 24 hours by default. These documented cache behaviors sit alongside the explicit incompatibility with password protection.
How can you check the conflicting setting?
Start in the site's MyKinsta controls. The password guide documents this path:
Sites > sitename > Tools > Password protection
The CDN documentation gives the CDN path as Sites > sitename > Caching > CDN > Enable CDN. The Edge Caching documentation gives the corresponding path as Sites > sitename > Caching > Edge Caching > Enable. Use the Caching area to check which of the two settings is active before trying to enable password protection. Kinsta's configuration documentation makes the state requirement explicit: password protection can be enabled only when neither named caching feature is enabled.
If the site needs password authentication, the documented configuration requires the CDN and Edge Caching conflict to be resolved first. If the site needs either caching feature, the password tool remains unavailable while that feature is enabled. The pages describe the incompatibility and the control paths, but do not document an exception for a URL, folder, or authenticated visitor.
Related terms
- How can custom server rules be added to a Kinsta-hosted site?
- Can MyKinsta redirects match a URL's query string?
- Cache-Control
FAQ
Does password protection cover only the WordPress admin?
No. Kinsta's htpasswd guide says the tool adds protection to the entire WordPress site. It also says the tool is available for live sites and staging environments.
What happens when a visitor cancels the login prompt?
Kinsta documents a 401 HTTP status code and a “401 Authorization Required” message when the credentials prompt is closed or canceled. A wrong username or password causes the prompt to appear again.
Can the credentials be changed later?
Yes. The guide says you can change the credentials or disable password protection from the .htpasswd tool in MyKinsta by clicking Modify.
Sources
- Kinsta, "Configuration Changes", July 1, 2025
- Kinsta, "htpasswd Protection", September 24, 2024
- Kinsta, "Kinsta CDN", May 28, 2026
- Kinsta, "Edge Caching", May 28, 2026
Check how a page reads to answer engines. Open the GEO score analyzer