WP Ghost auto-detects your server type, but you can override it manually if detection fails or custom paths aren’t working correctly. WP Ghost generates different rewrite rules depending on whether your server runs Apache, Nginx, LiteSpeed, IIS, or a managed hosting environment like SiteGround, WP Engine, or Flywheel. In most cases, auto-detection works and you never need to touch this setting. When it doesn’t, selecting the correct server type fixes path-related issues immediately. This is a free feature.
What Is the Server Type Setting?
The Server Type setting tells WP Ghost which web server software your hosting uses. This determines how WP Ghost generates rewrite rules for custom paths. Apache uses .htaccess rules, Nginx uses location blocks, LiteSpeed reads .htaccess with its own engine, and IIS uses web.config. Some managed hosting providers (SiteGround, WP Engine, Flywheel, CloudPanel) have provider-specific configurations that WP Ghost handles with dedicated profiles.
When to Change the Server Type
WP Ghost’s automatic detection is accurate for most hosting environments. You only need to change it manually in two situations:
Detection error. WP Ghost misidentifies your server type when saving settings. This can happen on hosting platforms that run Nginx as a reverse proxy in front of Apache, or on custom server stacks where the PHP $_SERVER variable doesn’t accurately reflect the actual web server.
Path or rewrite issues. You’ve activated Safe Mode or Ghost Mode, but custom paths return 404 errors, the site layout breaks, or pages load without CSS/JS. The wrong server type means WP Ghost writes rewrite rules in a format your server can’t process.
Supported Server Types
WP Ghost includes dedicated profiles for:
General server types: Apache, Nginx, LiteSpeed, IIS Windows.
Hosting-specific profiles: SiteGround, CloudPanel, Flywheel, InMotion, WP Engine, AWS Bitnami, GoDaddy.
If your hosting provider isn’t listed, no special configuration is needed. Select one of the primary server types: Apache, Nginx, or IIS. Most hosting providers run one of these three. If you’re not sure which one, see “How to Identify Your Server Type” below.
How to Select Your Server Type
- Go to WP Ghost > Advanced > Compatibility.
- Select the correct server type from the Server Type dropdown.
- Click Save.
After saving, WP Ghost regenerates rewrite rules for the selected server type. If you have Safe Mode or Ghost Mode active, verify your site by opening an incognito browser and checking the homepage, a few internal pages, and the custom login path.
How to Identify Your Server Type
If you don’t know which server your hosting uses, there are a few quick ways to find out:
Check your hosting panel. Most hosting dashboards (cPanel, Plesk, hPanel) display the server software on the main page or in the server information section.
Check WordPress Site Health. Go to Tools > Site Health > Info > Server. The “Server architecture” and “Web server” fields show your server software and version.
Ask your hosting provider. Contact support and ask: “What web server software does my hosting use – Apache, Nginx, LiteSpeed, or something else?” They’ll confirm immediately.
Quick reference for common providers: SiteGround uses Nginx, WP Engine uses Nginx, Flywheel uses Nginx, GoDaddy uses Apache (shared) or Nginx (managed), Bluehost uses Apache, InMotion uses Apache, Cloudways varies by stack choice (Apache, Nginx, or LiteSpeed), AWS Bitnami uses Apache by default.
Troubleshooting
Custom paths return 404 after activating Safe Mode or Ghost Mode
The most common cause is wrong server type. Go to Advanced > Compatibility and verify the server type matches your hosting. If you’re on a reverse proxy setup (Nginx in front of Apache), try selecting Nginx instead of Apache. After changing, save and test in an incognito browser. If the issue persists, use the rollback settings to revert and try a different server type.
Site layout breaks after saving with a new server type
The rewrite rules generated for the new server type aren’t being processed correctly. Enable Prevent Broken Website Layout in Rollback Settings to protect the frontend while you troubleshoot. If you need emergency access, use the emergency disable guide or add a constant in wp-config.php.
Hosting provider uses Nginx as reverse proxy with Apache
Some hosting setups run Nginx as the frontend proxy and Apache behind it. WP Ghost may detect Apache while the rewrite rules need to target Nginx (or vice versa). Try both server types and test after each change. If your provider is listed as a hosting-specific profile (SiteGround, WP Engine, etc.), use that profile instead of a generic server type.
Frequently Asked Questions
Does WP Ghost auto-detect my server type?
Yes. WP Ghost reads PHP server variables to determine your server type automatically. For most hosting environments this is accurate and you never need to change it. Manual selection is only needed when auto-detection fails or when path-related issues occur after activating Safe Mode or Ghost Mode.
My hosting provider isn’t listed. What do I select?
Select one of the three primary server types: Apache, Nginx, or IIS. The hosting-specific profiles (SiteGround, WP Engine, etc.) are convenience options that pre-configure settings for those platforms. Any hosting provider runs one of the three primary servers under the hood.
I’m on Nginx but can’t edit nginx.conf. What should I do?
Select Nginx as the server type, but use WP Ghost’s non-rewrite features only. See Use WP Ghost on Nginx Without Config Changes for a complete guide. For full path-security features on Nginx, see Setup WP Ghost on Nginx Server.
Does this work with WooCommerce?
Yes. The server type setting affects how rewrite rules are generated, not WooCommerce functionality. WP Ghost is fully compatible with WooCommerce on all supported server types.
Does WP Ghost modify WordPress core files?
No. Server type selection determines which format WP Ghost uses for rewrite rules (e.g., .htaccess on Apache, config instructions for Nginx). No WordPress core files are modified. Changing the server type regenerates rewrite rules but leaves all WordPress files untouched.
Related Tutorials
Server setup and compatibility:
- Setup WP Ghost on Nginx Server – Full Nginx configuration with rewrite rules.
- Use WP Ghost on Nginx Without Config Changes – For managed Nginx hosting where you can’t edit config files.
- Set AllowOverride All on Apache – Required Apache setting for .htaccess rules to work.
- Rollback Settings – Recover if a server type change breaks your site.
- WP Ghost Compatibility Plugins List – Known plugin compatibility for different server environments.