WP Ghost on Nginx VPS Setup Guide

WP Ghost works on Nginx VPS (Virtual Private Server) environments with full root access. When you have SSH access and can edit Nginx config files directly, you add an include line pointing to WP Ghost’s hidemywp.conf file in your site’s server block. This is different from managed hosting (Kinsta, WPMUDEV, Flywheel) where you can’t edit Nginx config files. With VPS access, the setup is straightforward and gives you full control over WP Ghost’s path security features.

Nginx Configuration File Structure

The typical Nginx directory structure:

/etc/nginx/
├── nginx.conf              # Main config (includes other files)
├── conf.d/                 # Additional config files (*.conf)
├── sites-available/        # Site configs (create here)
├── sites-enabled/          # Active sites (symlinks to sites-available)
├── fastcgi_params
├── mime.types
└── ...

The nginx.conf file typically ends with these include directives that load your site configs:

include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;

Step 1: Activate WP Ghost and Generate the Config

1. Install and activate the WP Ghost plugin.
2. Go to WP Ghost > Change Paths > Level of Security.
3. Select Safe Mode or Ghost Mode and customize paths.
4. Click Save.
5. WP Ghost generates a hidemywp.conf file in your WordPress root directory and displays the include line you need to add.

Step 2: Add the Include to Your Server Block

SSH into your server and open your site’s Nginx server block config:

sudo nano /etc/nginx/sites-available/yoursite

Add the include line before the location / block, inside the server { } block:

server {
    listen 80;
    server_name yourdomain.com;
    root /var/www/yoursite;
    index index.php;

    # WP Ghost rewrite rules (add this line)
    include /var/www/yoursite/hidemywp.conf;

    location / {
        try_files $uri $uri/ /index.php?$args;
    }

    location ~ \.php$ {
        fastcgi_pass 127.0.0.1:9000;
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }
}

Use the exact include path from WP Ghost’s notification. The path depends on your WordPress installation directory. The example above uses /var/www/yoursite/, but your path may be /var/www/html/, /home/user/public_html/, or another location. Always copy the include line directly from WP Ghost’s notification.

Placement matters. The include line must be placed before the location / block. Nginx processes location blocks in a specific order, and WP Ghost’s rewrite rules need to be evaluated before the WordPress try_files rule catches the request.

Step 3: Test and Reload Nginx

1. Test the Nginx config for syntax errors:

sudo nginx -t

2. If the output shows syntax is ok and test is successful, reload Nginx:

sudo nginx -s reload

3. Go back to WP Ghost and run the Frontend Login Test.
4. If everything loads correctly, click “Yes, it’s working”.
5. If something is broken, click “No, abort” to roll back.

Use reload, not restart. Reloading applies the new config without dropping active connections. Restarting terminates all connections and starts fresh, which causes brief downtime. Always use nginx -s reload in production.

Troubleshooting

Nginx syntax error after adding the include

The hidemywp.conf file may not exist at the specified path. Verify with ls -la /var/www/yoursite/hidemywp.conf. If it doesn’t exist, re-save WP Ghost settings to regenerate it. Also ensure the include line is inside the server { } block, not outside it.

Custom paths return 404

The include line may be placed after the location / block. Move it before location / so WP Ghost’s rewrite rules are evaluated first. Reload Nginx after moving it.

File permissions prevent Nginx from reading hidemywp.conf

The Nginx worker process runs as the www-data user (or nginx on some distributions). Ensure the hidemywp.conf file is readable by Nginx: sudo chown www-data:www-data /var/www/yoursite/hidemywp.conf and sudo chmod 644 /var/www/yoursite/hidemywp.conf.

Need to reload Nginx after every WP Ghost save

Yes, this is expected. Nginx loads its config at startup and keeps it in memory. Any changes to hidemywp.conf (which WP Ghost updates when you save) require a reload: sudo nginx -s reload. This is different from Apache, which re-reads .htaccess on every request.

Locked out after configuration

SSH into your server and either remove the include line from the server block and reload Nginx, or use the Safe URL parameter to bypass WP Ghost temporarily. See the Emergency Disable guide for additional recovery methods.

Frequently Asked Questions

Do I need to reload Nginx every time I save WP Ghost settings?

Yes, whenever you change path settings. WP Ghost updates the hidemywp.conf file automatically, but Nginx doesn’t detect file changes until it’s reloaded. Run sudo nginx -s reload after any path change. Non-path settings (firewall, brute force, 2FA) don’t require a Nginx reload.

How is this different from the Custom Nginx Config File guide?

The Custom Nginx Config File guide covers the same core process but is written for managed Nginx hosting where you may have limited access. This VPS guide includes more Nginx configuration context (directory structure, server blocks, includes) for users who manage their own server and may be less familiar with Nginx conventions.

What if I don’t have root access?

If you’re on managed hosting without Nginx config access (Kinsta, WPMUDEV, Flywheel), see Use WP Ghost on Nginx Without Config Changes for features that work without server config modifications, or contact your hosting support to add the include.

Does WP Ghost modify WordPress core files?

No. WP Ghost generates a separate hidemywp.conf file and uses WordPress hooks for application-level changes. No core files are modified. Deactivating WP Ghost restores all defaults instantly.

Related Tutorials

Nginx and server configuration:

• Custom Nginx Config File – Standard Nginx setup guide (more concise version).
• Use WP Ghost on Nginx Without Config Changes – For managed hosting without config access.
• Kinsta Server Setup – Managed Nginx hosting via support.
• Safe URL Parameter – Bypass WP Ghost temporarily if needed.
• Emergency Disable – Recovery via SSH if needed.