Set Up WP Ghost on Kinsta Hosting – Nginx Configuration via Support

Moved

This tutorial has moved to the new WP Ghost Knowledge Base where each feature is presented in detail.

View on new site

WP Ghost (formerly Hide My WP Ghost) works on Kinsta hosting. Kinsta uses Nginx and does not provide direct access to the server config. You need to send the hidemywp.conf file to Kinsta support so they can add it to your Nginx configuration. This is a one-time setup — Kinsta’s support team typically handles it within minutes.

How to Set Up WP Ghost on Kinsta

Step 1: Configure and Save WP Ghost Settings

Install WP Ghost. Go to WP Ghost > Change Paths > Level of Security. Select Safe Mode or Ghost Mode. Customize your paths or keep the defaults. Click Save.

WP Ghost settings saved with custom paths configured on Kinsta

Step 2: Download the hidemywp.conf File

After saving, WP Ghost generates a hidemywp.conf file in your website root directory. Download this file using Kinsta’s File Manager (in MyKinsta dashboard) or via SFTP.

Kinsta File Manager showing the hidemywp.conf file in the website root directory

Step 3: Send the File to Kinsta Support

Contact Kinsta’s support team and send them the hidemywp.conf file. Ask them to include it in your site’s Nginx configuration and restart the server. Kinsta support typically handles this within minutes.

Step 4: Back Up Settings and Wait

Back up your WP Ghost settings from WP Ghost > Backup / Restore. Deactivate the plugin while waiting for Kinsta to add the rules. This prevents path errors while the server config is being updated.

Step 5: Reactivate and Verify

Once Kinsta confirms the rules are added, reactivate WP Ghost and restore your settings from WP Ghost > Backup / Restore. Verify that the login page works with the new path and that the frontend loads correctly. Open a private browser and view source to confirm no /wp-content/ references remain.

WP Ghost frontend and login verification after Kinsta Nginx configuration

Troubleshooting

Paths not working after Kinsta added the file. Kinsta may need to restart Nginx after adding the include. Confirm with support that the server was restarted. Also clear Kinsta’s page cache from the MyKinsta dashboard.

Login page returns 404. The hidemywp.conf file may not match your current WP Ghost settings (e.g., if you changed paths after generating the file). Re-save WP Ghost settings to regenerate the conf file, send the updated file to Kinsta support.

Locked out after configuration. Use the Safe URL parameter or contact Kinsta support to remove the hidemywp.conf include. See the Emergency Disable guide.


Frequently Asked Questions

Is this a one-time setup?

The initial include is one-time. WP Ghost updates the hidemywp.conf file automatically when you change settings. However, Kinsta may need to restart Nginx for certain rewrite rule changes to take effect. Check with Kinsta support if paths stop working after a settings change.

Do I need to contact Kinsta support every time I change paths?

Not necessarily. WP Ghost updates hidemywp.conf automatically. Many path changes take effect without a server restart. If a specific change does not work, contact Kinsta to restart Nginx.

Does this work with Kinsta’s CDN?

Yes. Kinsta’s CDN serves assets from its edge network. After WP Ghost changes paths, clear the Kinsta CDN cache from the MyKinsta dashboard. If CDN URLs still show old paths, add the CDN domain in WP Ghost > Mapping > CDN URLs.

Does WP Ghost modify WordPress core files?

No. WP Ghost generates a separate hidemywp.conf file. No core files modified. Removing the include from Nginx restores all defaults.


Nginx Server Setup – general Nginx configuration for WP Ghost.

Customize All WordPress Paths – configure paths after server setup.

Compatibility Plugins List – hosting-specific notes.

Emergency Disable Guide – recovery if configuration causes issues.

Website Security Check – verify your configuration after setup.