Is WP Ghost Compatible with Kinsta Hosting?
This tutorial has moved to the new WP Ghost Knowledge Base where each feature is presented in detail.
Yes. Kinsta runs Nginx and doesn’t give you access to its config, so for full path changes Kinsta support adds WP Ghost’s hidemywp.conf include for you. Without that, the Minimal (No Config Rewrites) preset still gives you the protection that needs no server rules.
Why does Kinsta require extra setup for WP Ghost?
Kinsta is a managed WordPress hosting provider that runs on Nginx. Unlike Apache servers where WP Ghost writes rewrite rules to .htaccess automatically, Nginx requires rules to be added to the server configuration file. Kinsta doesn’t give you direct access to nginx.conf, so you need to contact their support team and ask them to include WP Ghost’s config file.
This is a one-time setup. Once Kinsta adds the config include, WP Ghost manages the rules automatically from that point on. You only need to contact Kinsta again if you change hosting plans or migrate to a different server.
How do I set up WP Ghost on Kinsta step by step?
Step 1 – Install and configure WP Ghost
Install the WP Ghost plugin on your Kinsta-hosted site. Go to WP Ghost > Change Paths > Level of Security and select your desired security level (Safe Mode or Ghost Mode). Customize any paths you want to change and click Save. After saving, WP Ghost generates a hidemywp.conf file and displays the Nginx setup notification.
Step 2 – Download the config file
Go to your website’s root directory using a file manager (Kinsta’s dashboard includes one, or use SFTP). Download the hidemywp.conf file that WP Ghost generated. This file contains all the Nginx rewrite rules needed for your custom paths.
Step 3 – Contact Kinsta support
Open a support ticket with Kinsta and send them the hidemywp.conf file. Ask them to include it in the Nginx configuration for your site and restart the server. Only the host can add rules to the Nginx config and restart the Nginx service.
Step 4 – Back up and deactivate while waiting
Before Kinsta applies the changes, back up your WP Ghost settings from WP Ghost > Backup/Restore and deactivate the plugin. This prevents any path conflicts while the rewrite rules aren’t yet loaded on the server. Keep the plugin deactivated until Kinsta confirms the rules are in place.
Step 5 – Activate and restore
Once Kinsta confirms the rules have been added, activate WP Ghost again and restore your saved settings from WP Ghost > Backup/Restore. Then run a frontend test: go to WP Ghost > Change Paths and click the Frontend Test button to verify that the new paths are loading correctly.
What if I don’t want to contact Kinsta support?
If you prefer to skip the Nginx config step, you can still use many of WP Ghost’s security features without rewrite rules. Custom login paths, brute force protection with reCAPTCHA, the 2026 Ghost Firewall, two-factor authentication, security headers, and version hiding all work through WordPress hooks and don’t require any server configuration changes.
WP Ghost includes a Minimal (No Config Rewrites) preset that configures exactly these features. Go to WP Ghost > Change Paths, select the Minimal preset, and click Load Preset. This gives you strong protection without needing to contact Kinsta at all.
For the full guide on this approach, see using WP Ghost on Nginx without config changes. For the complete Kinsta setup tutorial, see the Kinsta server setup guide.
Frequently asked questions
Will Kinsta support add the WP Ghost config file?
Ask Kinsta support to include it. If they hesitate, explain that it’s a single include file with URL rewrite rules that changes nothing beyond path routing.
Do I need to contact Kinsta every time I change WP Ghost settings?
No. Kinsta adds the include once. When you change paths later, WP Ghost rewrites hidemywp.conf, but Nginx reads it only when it reloads, so ask Kinsta support to reload Nginx after a path change.
Is WP Ghost still effective on Kinsta without the Nginx config?
Yes. Without config rewrites you lose full path hiding (renaming wp-content, wp-includes, etc.), but custom login paths, brute force protection, firewall, 2FA, security headers, and version hiding all work through WordPress hooks. These features cover the most critical attack vectors.
Does this work with WooCommerce on Kinsta?
Yes. WP Ghost is fully compatible with WooCommerce on Kinsta. Cart, checkout, product pages, and customer accounts all work normally with both the full Nginx setup and the minimal no-config approach.
Does WP Ghost modify WordPress core files?
No. WP Ghost uses server rewrite rules (via the hidemywp.conf file on Nginx) and WordPress filters to change paths at runtime. No core files, theme files, or plugin files are modified. Deactivating WP Ghost restores all default paths instantly.