What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To make WordPress post-name and other “pretty” URLs work on Nginx, route requests that are not real files or directories to WordPress’s front controller. In a single-site server block, that normally means:
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
location / {
try_files $uri $uri/ /index.php?$args;
}Nginx does not read Apache-style .htaccess files, so this rule must be present in the active Nginx configuration. WordPress stores the permalink structure; Nginx supplies the request routing, and PHP-FPM executes index.php.
As an Amazon Associate I earn from qualifying purchases.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWhat clean permalinks require
A permalink is the permanent URL used for a WordPress post, page, category, tag, or other archive. You choose the structure in WordPress, but the web server must pass a request such as /news/example-post/ to WordPress instead of looking for a directory with that literal name.
The working chain has three separate parts:
- WordPress settings: the selected built-in or custom structure is stored by WordPress.
- Nginx routing: the server decides whether a request is a real filesystem object or should be sent to WordPress.
- PHP handling: PHP-FPM or another PHP upstream runs the requested PHP script.
WordPress documents permalinks as permanent URLs for posts, pages, categories, and other archives in its permalink documentation. Nginx has no directory-level equivalent to Apache’s .htaccess; WordPress Developer Resources explicitly notes that “with Nginx there is no directory-level configuration file like Apache’s .htaccess or IIS’s web.config files” (WordPress Nginx guidance). Consequently, a WordPress administrator cannot make Nginx rewrite rules appear simply by saving Permalinks.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
The standard single-site Nginx rule
For a normal installation whose document root contains index.php, place this location in the active server {} block:
location / {
try_files $uri $uri/ /index.php?$args;
}This is the usual clean-permalink rule recommended in WordPress’s Nginx material and also described by Learn WordPress.
Recommended Free Tools
What each operand does
| Part | Purpose | Typical request |
|---|---|---|
$uri |
Serve an existing file directly. | /wp-content/uploads/photo.jpg |
$uri/ |
Serve an existing directory directly. | /wp-admin/ |
/index.php?$args |
Send anything else to WordPress’s front controller while retaining the original query string. | /sample-post/?preview=true |
The first two checks prevent every image, stylesheet, JavaScript file, and real directory from being processed by WordPress. If neither exists, the final operand hands the virtual URL to index.php. The ?$args suffix preserves query arguments; WordPress’s official Nginx page specifically calls out this part as necessary so non-default permalink structures do not lose their query string (official guidance).
Build the server block in the right order
1. Point root at the WordPress files
The server’s root must be the directory that contains the WordPress index.php used by the site. A mismatched root is a common reason the home page, assets, or fallback behave inconsistently.
server {
listen 80;
server_name example.com www.example.com;
root /var/www/example;
index index.php;
location / {
try_files $uri $uri/ /index.php?$args;
}
}Use your distribution’s existing TLS, logging, and security settings as appropriate; the important values for permalink routing are the correct root, index index.php, and the location / fallback. Do not copy a root path from another server unless it is the directory actually containing this installation.
2. Add PHP-FPM handling separately
The permalink location only chooses where a request goes. Nginx still needs a PHP location that passes PHP requests to the PHP-FPM socket or to a configured PHP upstream. A common pattern is:
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
location ~ .php$ {
try_files $uri =404;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_pass unix:/run/php/php-fpm.sock;
}The socket path, include filename, and upstream name vary by operating system and PHP version, so use the values installed on your server. The important safety check is try_files $uri =404; inside the PHP location: it prevents Nginx from sending a nonexistent script to PHP-FPM. This check belongs in the PHP location, not in the general location / block.
If you replace the general fallback with try_files $uri =404;, a virtual post or page URL will stop at Nginx and return a 404 before WordPress can resolve it. Keep the two locations’ jobs distinct: location / routes unknown paths to index.php; the PHP location verifies and executes actual PHP files.
3. Validate before reloading
Run the syntax test provided by your platform, commonly nginx -t, before asking Nginx to reload. Fix every reported error first. Then reload Nginx using the service manager for your system. A successful syntax test confirms that the configuration parses; it does not prove that the intended server {} block, root directory, PHP socket, or DNS name is being used.
Save the permalink structure in WordPress
- Sign in to the WordPress dashboard.
- Open Settings > Permalinks.
- Select the built-in structure you want, or enter a custom structure such as a post-name pattern.
- Click Save Changes, even if the desired option already appears selected.
Saving causes WordPress to store the structure and refresh its rewrite-related settings. Nginx does not receive a generated .htaccess file, so the server-block rule remains your responsibility. After saving, test a post, a page, an archive, and a static asset rather than only the front page.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsSubdirectory installations
When WordPress is installed under a path such as /my_subdir instead of directly in the document root, the fallback must name that installation’s front controller. For example:
location / {
try_files $uri $uri/ /my_subdir/index.php?$args;
}Use the exact URL and filesystem model for your installation. The official Giving WordPress Its Own Directory documentation supplies the corresponding Nginx pattern. Do not blindly combine a document-root installation’s /index.php fallback with a subdirectory layout; that can send requests to the wrong application or produce a direct 404.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Distinguish URL path from filesystem path
The fallback shown above is a URL path beginning with /, not an operating-system path such as /var/www/my_subdir/index.php. Nginx resolves it through the configured server root and location processing. Keep the URL prefix, trailing slash behavior, and WordPress “site address” settings consistent with the installation.
Testing checklist after the change
Use a small, repeatable set of URLs and record which layer fails:
Free tools Windows power users keep installed
One-click scans. No signup required.
- Home page: confirms that the server name and root reach the expected site.
- One post: exercises the permalink fallback.
- One page: confirms that routing is not limited to post requests.
- An archive: test a category, tag, date, or author archive.
- A known static file: open an image, stylesheet, or JavaScript URL to verify that real files bypass WordPress.
- A query-string URL: use a legitimate parameter, such as a preview or tracking parameter, to verify that arguments survive the fallback.
- A PHP endpoint you intentionally use: confirm that PHP-FPM executes it rather than downloading the source or returning a direct Nginx error.
Test both the canonical hostname and any alternate hostname that should redirect. If a reverse proxy or cache sits in front of Nginx, test through that public path as well as, where possible, directly against the origin; an upstream layer can cache an old 404 or route to a different server block.
Why pretty URLs return 404 on Nginx
Every post and page is a 404
- Verify that the request reaches the intended
server {}block for its hostname and port. - Confirm that
location /ends with/index.php?$argsfor a document-root installation, or the correct subdirectory front controller. - Check that the root directory contains the referenced
index.php. - Confirm that PHP-FPM is reachable and that the PHP location is not intercepting the request with
try_files $uri =404;. - Open Settings > Permalinks and save the selected structure again.
The home page works, but internal URLs fail
This pattern usually means the root and PHP entry point work while virtual paths are not being routed. Inspect the active location /, not just a configuration file on disk. An included file, a more specific location, or a different virtual host may be handling the request. The fallback must be in the configuration Nginx actually loaded.
A PHP file downloads or Nginx returns a direct PHP 404
Inspect the PHP location’s regular expression, FastCGI parameter include, SCRIPT_FILENAME, socket or TCP upstream, and filesystem permissions. A downloaded PHP file means Nginx is serving it as static content instead of passing it to PHP-FPM; a direct 404 can mean the script check is using the wrong root or the requested file truly does not exist.
Only a migrated or recently changed site fails
Compare the current active configuration with the old host, including the root path, hostname, PHP version, socket name, and any included snippets. Review recent plugin or theme changes and migration edits. WordPress’s common-errors guidance recommends resetting permalinks and investigating configuration-related causes for this class of failure.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Static assets fail after adding regex locations
A broad regular-expression location can intercept requests that should have reached the normal static-file or PHP handling. Check that your static-file rules do not capture PHP requests or rewrite virtual WordPress paths incorrectly. Nginx’s try_files documentation explains how existing files and directories are distinguished from fallback or error handling (Nginx static-content guide). Remove or narrow a conflicting location before changing the WordPress fallback.
Choosing the right configuration for your layout
| Situation | Fallback concept | What to verify |
|---|---|---|
| Single site in the document root | /index.php?$args |
The configured root contains the WordPress front controller. |
| WordPress in a subdirectory | /my_subdir/index.php?$args or the exact installation prefix |
The URL prefix and WordPress directory settings match. |
| Multisite | Path-specific rules based on the network’s subdomain or subdirectory model | Network configuration, domain mapping, and any required Nginx rules. |
| PHP-FPM over a Unix socket | PHP location passes to the installed socket | Socket path, ownership, permissions, and service status. |
| PHP-FPM over TCP | PHP location passes to the configured host and port | Upstream address, firewall rules, and listener availability. |
| Reverse proxy or cache in front | Origin still uses the normal WordPress fallback | Forwarded host, cache behavior, HTTPS redirects, and stale cached errors. |
The core single-site rule does not change merely because PHP uses a socket instead of TCP. Subdirectory and multisite layouts are different because the front-controller path and request model are different. For multisite, do not paste a single-site snippet and assume it covers network-specific paths; apply the network’s documented, path-specific design and test each site URL.
Operational and security considerations
Keep the PHP check narrow
Only the PHP location should execute PHP scripts. Retain a file-existence check and pass a correctly constructed SCRIPT_FILENAME. This reduces the chance that a request for a nonexistent or unintended script is forwarded to PHP-FPM.
Do not hide configuration errors with extra rewrites
Adding multiple fallback rewrites, broad regex locations, or ad-hoc 404 handlers can make it unclear which rule processed a request. Start with one general location / and one PHP location, then add exceptions only when a documented application requirement demands them.
Read the logs at the right layer
Nginx access and error logs show which server handled the request and whether the upstream connection failed. PHP-FPM logs show script and worker errors. WordPress logs or debugging output can reveal application-level routing problems. Correlate timestamps and the exact URL, including its query string, rather than testing a different path and drawing a conclusion.
When managed hosting handles the server block
If you do not administer Nginx, the provider or platform team may own the server block, PHP-FPM pool, reload process, and cache configuration. Give them the exact failing URL, expected permalink structure, hostname, whether the installation is in a subdirectory, and the time of the error. Ask them to verify the active server block and its try_files fallback rather than only resetting WordPress settings. A managed WordPress hosting service can be useful when you need someone else to maintain these server-level details, but the required behavior remains the same: real files and directories are served directly, and other paths reach the correct WordPress front controller.
Complete deployment sequence
- Identify the active Nginx server block for the site’s hostname.
- Set
rootto the directory containing the intended WordPressindex.phpand addindex index.php. - For a document-root single site, add
location / { try_files $uri $uri/ /index.php?$args; }; for a subdirectory install, replace the fallback with that installation’s front-controller URL. - Configure a separate PHP location with the platform’s FastCGI parameters, the correct PHP-FPM socket or TCP upstream, and an appropriate
try_files $uri =404;check. - Run the platform’s Nginx syntax test and correct all errors.
- Reload Nginx only after validation succeeds.
- In WordPress, open Settings > Permalinks, select the desired structure, and save it.
- Test the home page, a post, a page, an archive, a static asset, and a URL carrying a query string.
- If a test fails, determine whether the request reached the wrong server block, missed the fallback, failed PHP-FPM, or was intercepted by a proxy, cache, or conflicting location.
There is no published task-specific benchmark establishing a speed or reliability advantage for one of these snippets over another. The practical requirement is correct request routing for the site’s actual layout, followed by verification at every layer that handles the request.
Frequently Asked Questions
Do I need an .htaccess file for WordPress on Nginx?
No. Nginx does not use Apache’s .htaccess mechanism. Configure the rewrite behavior in the active Nginx server block instead.
Why is `?$args` included in the fallback?
It forwards the original query string when Nginx sends a virtual URL to `index.php`, preventing valid parameters from being dropped.
Can I use `try_files $uri =404;` in `location /`?
No. That would return 404 for virtual post and page URLs. Use the WordPress fallback in `location /`; reserve the file-existence check for the PHP location.
What changes when WordPress is installed in a subdirectory?
The fallback must point to that installation’s front controller, such as `/my_subdir/index.php?$args`, using the exact path documented for the site.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
