iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
If your WordPress homepage loads on Nginx but every post, page, feed, or /wp-admin/ URL returns 404, the usual cause is an incomplete try_files rule. Nginx is checking the filesystem and stopping at =404 instead of sending unknown paths to WordPress. For a standard installation in the domain root, change the active server block to use try_files $uri $uri/ /index.php?$args;, verify the PHP handler and document root, test the configuration, reload Nginx, and retest representative URLs.
Why the homepage works while every other URL returns 404
WordPress uses a front controller: index.php receives a request and determines which post, page, feed, archive, or administrative screen should be displayed. The homepage often appears to work because / maps directly to the real file index.php. A pretty permalink such as /about/ usually is not a physical file or directory. Nginx must therefore pass that request to WordPress rather than treating the missing filesystem path as a final error.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →A common broken rule looks like this:
location / {
try_files $uri $uri/ =404;
}try_files checks the requested URI and then the URI with a trailing slash. If neither exists, =404 immediately sends an Nginx-generated 404 response. WordPress never receives the request, so changing a theme, refreshing permalinks, or editing a plugin cannot solve the routing failure.
For a root-level WordPress installation, the final fallback must be /index.php?$args. That tells Nginx to execute WordPress’s front controller while preserving the original query string. The fallback belongs in the server’s Nginx configuration, not in a per-directory file.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
What you need before changing Nginx
Make the change only if you can identify and reload the virtual host that actually serves the affected domain. You normally need shell access with permission to read the loaded Nginx configuration, edit the relevant server block, run a syntax test, and reload the service. You also need access to the WordPress document root and the PHP-FPM socket or upstream used by that virtual host.
- Record the current configuration or create a backup before editing it.
- Know the hostname that produces the error, including whether it uses
wwwor a non-wwwname. - Know the absolute document root and confirm it contains WordPress’s
index.php. - Know the configured PHP-FPM socket or application upstream; its path differs by operating system and PHP version.
- Have a way to reload Nginx and to undo the edit if the syntax test or application check fails.
Do not assume that a file named default, wordpress.conf, or site.conf is active. A correct rule in an unused file has no effect.
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 minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Find the active server block
Start with the virtual host selected for the failing hostname. The active block must contain the matching server_name and the document root used by this WordPress site. Inspect the complete loaded configuration rather than only one include file, because distribution packages commonly assemble Nginx settings from several directories.
- Identify the server block whose
server_namematches the requested domain. - Check its
rootdirective and list that directory. The same directory should containindex.php,wp-admin,wp-content, andwp-includesfor a normal installation. - Inspect every
locationblock inherited or included by that server. A more-specific location can take precedence overlocation /. - Confirm that the block is loaded by the Nginx configuration used by the running service, not merely present on disk.
If the root points to a parent directory, an old release directory, or a different site, the rewrite can be syntactically correct and still send requests to the wrong files.
Use the correct single-site configuration
For WordPress installed at the domain root, the essential pattern is:
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
server {
server_name example.com www.example.com;
root /var/www/example.com/htdocs;
index index.php;
location / {
try_files $uri $uri/ /index.php?$args;
}
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;
}
}Replace the hostname, document root, and PHP-FPM socket with the values used by your deployment. The socket shown is an example, not a universal path. Some systems use a versioned socket, a TCP address, or a named upstream.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →| Directive | Purpose | What to verify |
|---|---|---|
root |
Sets the filesystem directory from which Nginx serves the site. | It is the directory containing this installation’s index.php and WordPress directories. |
index index.php |
Allows a directory request such as / to resolve to the WordPress front controller. |
The file exists and is readable by the Nginx worker user. |
location / |
Handles ordinary site requests, including pretty permalinks. | No later fallback ends in =404 for normal WordPress URLs. |
try_files $uri $uri/ /index.php?$args; |
Serves real files and directories directly, then routes virtual WordPress paths to index.php with the query string preserved. |
The fallback includes the leading slash and ?$args. |
location ~ .php$ |
Sends PHP scripts to PHP-FPM or the configured upstream. | The handler can execute the same index.php in the configured root. |
try_files $uri =404 inside the PHP location |
Prevents requests for nonexistent PHP files from being passed to PHP-FPM. | Keep this security check while fixing the outer location / fallback. |
fastcgi_param SCRIPT_FILENAME |
Provides PHP-FPM with the full script path. | The resulting path points into the same document root used by Nginx. |
fastcgi_pass |
Defines the PHP-FPM socket or upstream. | The endpoint exists, is listening, and matches the site’s PHP configuration. |
The security guard in the PHP location should remain. Removing it to make a test pass can expose arbitrary paths to PHP and masks a routing problem instead of correcting it.
Apply the repair safely
- Open the active server configuration. Edit the file that is actually included for the affected hostname. If your platform generates configuration, use its documented override mechanism rather than editing a generated file that will be replaced.
- Correct the outer location. In
location /, replace an unconditional file-miss fallback such astry_files $uri $uri/ =404;withtry_files $uri $uri/ /index.php?$args;. Keep existing rules for static assets only when they do not intercept WordPress routes. - Check the PHP location. Confirm that
index.phpis allowed through the PHP location and thatfastcgi_param SCRIPT_FILENAMEresolves under the configured root. Keeptry_files $uri =404;in this PHP block unless your deployment has a documented alternative. - Validate syntax. Run
nginx -t. Do not reload if it reports an error. Correct missing semicolons, unmatched braces, duplicate directives, invalid includes, or an incorrect socket path first. - Reload the running service. Use
nginx -s reloador the reload command supplied by your operating system or hosting platform. A reload applies the new configuration without intentionally stopping existing workers. - Retest the application. Request a known page, a post, a feed,
/wp-admin/, and both trailing-slash and no-slash forms where your permalink policy supports them. Use a private browser window or a command-line request so an old cached 404 does not mislead you. - Refresh WordPress’s permalink settings only as a final application check. In the dashboard, open Settings > Permalinks and save the intended structure. This can refresh WordPress’s rewrite state, but it cannot replace the Nginx front-controller rule.
How to tell which component is returning the 404
An Nginx file-miss response and a WordPress-generated 404 require different fixes. Compare the response headers, page body, and logs while requesting a URL that should exist.
- Nginx-level 404: often has a plain Nginx error page, appears before WordPress styling, and is accompanied by an entry in the Nginx error or access log showing that no file or location matched.
- WordPress-level 404: uses the site’s theme or WordPress error template, which means the request reached PHP. Investigate the slug, post status, taxonomy, canonical redirects, plugins, or WordPress rewrite behavior instead of changing
try_filesagain. - PHP failure: a 502, 504, blank response, or PHP error log entry points to PHP-FPM connectivity or code execution rather than URL routing.
Check logs at the same time as the request. If Nginx logs the request as a direct file miss, inspect the selected server block and its locations. If PHP logs the request, routing is working and the next diagnosis belongs inside WordPress or PHP.
Subdirectory installations need a different fallback
If WordPress is installed below the domain root, the fallback must include that installation prefix. For an installation in /my_subdir, the relevant pattern is:
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
location /my_subdir/ {
try_files $uri $uri/ /my_subdir/index.php?$args;
}The exact location structure depends on whether the rest of the domain serves another application. The root, location prefix, WordPress URL settings, and PHP script path must describe the same physical layout. A root-level fallback of /index.php?$args can send a subdirectory request to the wrong application.
Test URLs inside and outside the prefix. Confirm that a real static file under the subdirectory is served directly, while a virtual page under /my_subdir/ reaches that directory’s index.php. If the site was moved from the root into a folder, also review the WordPress Address and Site Address values before diagnosing rewrites.
Multisite requires topology-specific rules
Multisite is not a drop-in variation of the single-site snippet. Subdirectory networks, subdomain networks, domain-mapped networks, and older versus newer WordPress versions can require different Nginx locations, rewrite exceptions, and handling for wp-admin, wp-content, and static files. Use the WordPress Nginx handbook rules that match the network’s version and topology, then adapt paths to the active server block.
Do not copy a single-site rule into a multisite network merely because the main homepage loads. Verify a site on the network, a network-admin URL, uploads, and a second site’s permalink. A rule that works for the primary site can still route mapped or subdirectory sites incorrectly.
Free tools Windows power users keep installed
One-click scans. No signup required.
Common causes when the corrected rule still fails
The edited file is not loaded
Reloading successfully proves only that Nginx accepted some configuration; it does not prove that the request uses the file you edited. Recheck the matching hostname, enabled-site links, include statements, and any control panel or container that generates the live configuration. Confirm that the running service was reloaded after the edit.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
A more-specific location wins
Nginx location selection can send a request to a prefix or regular-expression location that bypasses location /. Review locations for language prefixes, security rules, static-only directories, legacy applications, and exact matches. A special location for /about/, for example, can continue returning 404 even when the general fallback is correct.
The document root and PHP root disagree
If Nginx serves files from one release directory but SCRIPT_FILENAME points to another, the homepage may appear while routed requests fail or PHP executes an unexpected copy of WordPress. Resolve the document root to an absolute path and verify that both Nginx and PHP-FPM reference the same installation.
Permalink structure or WordPress URLs are wrong
After routing reaches WordPress, check the selected structure under Settings > Permalinks, the WordPress Address, and the Site Address. A site moved between domains or directories can generate redirects or WordPress-level 404s even with a correct Nginx rule.
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 errorsA cache is serving an old 404
Browser, reverse-proxy, page-cache, and CDN layers can retain the previous response. First prove that the origin returns the correct page, then purge the affected cache and test again. A cache-purging plugin such as Nginx Helper can assist with invalidation, but it does not create the Nginx front-controller route and cannot repair a bad server block.
Trailing-slash behavior is being mistaken for routing failure
WordPress may canonicalize /about to /about/, or the reverse, depending on its settings and filters. Test the canonical form shown by the site and inspect redirect status codes. A redirect followed by a WordPress page is normal; a direct Nginx 404 on both forms indicates a routing or location problem.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Why editing .htaccess does not fix Nginx
Nginx does not process Apache’s per-directory .htaccess files. The WordPress Advanced Administration Handbook states: “With Nginx there is no directory-level configuration file like Apache’s .htaccess or IIS’s web.config files.” Nginx configuration is applied at the server level, so the rewrite must be expressed in the active server block’s location directive.
An .htaccess file may remain in a migrated WordPress directory, but changing it will not make Nginx route pretty URLs. Apache-to-Nginx migration guides that show Apache rewrite syntax are not substitutes for the Nginx try_files rule. Remove or ignore obsolete advice and inspect the configuration used by the running Nginx process.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Decide who should perform the repair
The technical fix is small, but the operational requirements determine whether self-service is appropriate. Use these criteria before handing the task to a provider.
| Option | Best fit | Capabilities to confirm | Trade-off |
|---|---|---|---|
| Self-managed repair | You administer the server and can edit, test, reload, and roll back Nginx. | Access to the active server block, PHP-FPM or upstream settings, logs, backups, and cache controls. | Fastest and least expensive when you already understand the deployment; a mistake can affect other virtual hosts. |
| Managed WordPress hosting | You lack server access or do not want to maintain Nginx and PHP-FPM. | Provider can inspect the live virtual host, support your WordPress path or multisite topology, reload safely, and manage origin and CDN caches. | Less direct control; resolution depends on the provider’s access and change process. |
| Configuration consultant | The site has custom routing, a migration, multisite, containerized Nginx, or several upstreams. | Documented backup and rollback, access to loaded configuration and logs, PHP-FPM knowledge, and a post-change test plan. | Higher one-time cost, but useful when a wrong location or topology makes a simple snippet unsafe. |
Whichever option you choose, require a configuration backup, a syntax test, a controlled reload, representative URL checks, and a rollback plan. The person making the change must be able to access the active server block and validate the PHP handler, not merely edit WordPress’s dashboard settings.
Final verification checklist
- The matching
server_nameis active for the failing hostname. - The
rootcontains the intended WordPressindex.php. location /usestry_files $uri $uri/ /index.php?$args;for a root installation.- No more-specific location intercepts the tested page or post.
- The PHP location retains its nonexistent-script guard and passes real scripts to the correct PHP-FPM socket or upstream.
nginx -tcompletes successfully before reload.- Nginx has been reloaded and the request is reaching the current process.
- A known page, post, feed,
/wp-admin/, and the site’s canonical slash form have been tested. - Logs show whether any remaining error is generated by Nginx, PHP, WordPress, or a cache.
- Subdirectory and multisite paths use rules written for their actual topology.
For the usual single-site, root-level installation, the decisive correction is the front-controller fallback. Once Nginx sends unknown paths to /index.php?$args and PHP-FPM executes that file from the same document root, WordPress can resolve its own permalinks instead of every virtual URL being rejected as a missing file.
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.
