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 reinstallA YOURLS short URL that returns 404 Not Found instead of redirecting is almost always a web-server routing problem, not a defect in YOURLS. The official YOURLS troubleshooting guidance describes this symptom as a configuration problem on the installation side. Start by identifying whether Apache, Nginx, a proxy, or YOURLS itself generated the 404, then correct the rewrite rules, path, override permissions, and PHP hand-off for your installation layout.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
The fastest reliable fix is to give YOURLS its own rewrite configuration, use the correct loader path for a root or subdirectory install, make sure Apache permits overrides (or place equivalent rules in the Nginx server block), and verify the result in the server logs.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What a YOURLS 404 actually means
When you open a valid short URL, YOURLS should process the slug and send an HTTP redirect to its long destination. A plain 404 means that request did not reach the redirect flow successfully. The failure can happen before PHP runs, while the web server is selecting a location, or because another application intercepted the request.
YOURLS’ official Frequent issues documentation says: “If you experience ‘404 not found’ instead of a redirection when you follow a short URL, this is not a bug. It’s a configuration problem on your end.”
#1 Best Overall
Sale
TOZO A1 Wireless Earbuds Bluetooth 5.3 Light Weight in Ear Headphones | IPX5 Waterproof,2 Mics for AI Calls,Immersive Premium Sound Bass Headset with Charging Case,32 EQ via App Black
- [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.
That statement does not identify one universal bad line. Virtual-host definitions, document roots, filesystem permissions, reverse proxies, PHP-FPM settings, and the exact YOURLS directory all vary. Use the procedure below to narrow the fault instead of repeatedly regenerating the short link.
Confirm the symptom before changing configuration
- Open a known-good short URL directly. Copy the complete URL into a private browser window or a second browser. Do not test only by clicking a cached page or an old bookmark.
- Record the response. Note the status code, the page title, any server signature, and whether the address changes. A successful YOURLS request normally changes to the destination URL; a 404 page that leaves the short URL in the address bar indicates failed routing.
- Test the YOURLS admin area separately. If the administration interface loads while short links fail, PHP and at least part of the installation are reachable. That narrows the problem to rewrite or path handling; it does not prove the public routing is correct.
- Check more than one slug. If every slug fails in the same way, suspect the server rule or virtual-host configuration. If one slug alone fails, verify that the slug exists and that you are testing the correct YOURLS database and domain.
Do not infer the cause from the wording of the 404 page alone. A page generated by the web server, a proxy, or an application can look similar. Browser developer tools’ Network panel, a request made directly to the endpoint, and the relevant access and error logs reveal which layer answered.
Free tools Windows power users keep installed
One-click scans. No signup required.
Collect the evidence that identifies the failing layer
Inspect the response in your browser
Open developer tools, select the Network panel, and request the short URL again. Record the status, response headers, and final response body. A server-generated 404 commonly has the server’s standard error layout; an application-generated response may include your site theme or a framework error page. Also check whether a proxy or CDN is listed in the response headers. This observation tells you where to look, but it does not replace the server logs.
Read the web-server logs at the time of a test
Check the access log and error log while requesting one failing slug. Look for the virtual host that received the request, the resolved request path, rewrite errors, permission denials, and upstream or PHP-FPM failures. YOURLS specifically recommends checking server logs for this symptom. Keep the exact timestamp and slug so you can match one request across multiple layers.
Verify the active document root
Many 404s come from editing a YOURLS directory that is not the directory used by the active virtual host. Confirm the domain and scheme in the short URL point to the intended virtual host, then confirm that host’s document root contains yourls-loader.php, the YOURLS files, and the intended .htaccess when using Apache. A second installation, staging directory, or old document root can otherwise make a correct rule appear ineffective.
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.
Fixing an Apache installation
Apache deployments need three things working together: the mod_rewrite module, a YOURLS-specific .htaccess, and permission for that file to override the directory configuration. Missing any one of these can produce a 404 for slugs even when the admin page works.
1. Enable and verify mod_rewrite
Ask your hosting provider or inspect the Apache module configuration to confirm mod_rewrite is enabled for the active server. If the module is unavailable, Apache will ignore rewrite directives and will look for a physical file matching the slug, which normally does not exist. The resulting 404 is expected until the module is enabled or equivalent rules are moved into the virtual-host configuration.
2. Give YOURLS its own .htaccess
The official server-configuration documentation states that YOURLS cannot share its root directory with another application whose rewrite rules are driven by .htaccess, such as WordPress. The file should contain YOURLS directives and no other rewrite rule. A competing application can capture the slug first, send it to a different front controller, or issue its own 404.
Place the YOURLS file in the directory that is the web root for the short-link host. Do not append unrelated site rules to that file. If the same domain must serve another application, use a separate domain or a dedicated subdirectory with a clearly separated configuration and matching paths.
3. Use the root-domain rule for a root install
For an installation whose files are directly in the virtual host’s document root, the essential pattern is:
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →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
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^.*$ /yourls-loader.php [L]
</IfModule>RewriteBase / tells Apache that the application begins at the domain root. The two conditions leave existing files and directories alone, while every other path is sent to /yourls-loader.php, where YOURLS can resolve the slug. Preserve the leading slash and the filename exactly as shown for a root install.
4. Use the subdirectory rule for a subdirectory install
If the files live below a path such as /somedir/, the base and loader must include that path:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /somedir/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^.*$ /somedir/yourls-loader.php [L]
</IfModule>Replace somedir with the actual directory name. A root-style RewriteBase / or a loader target that omits the directory sends the request to the wrong location and commonly produces a 404. Conversely, adding a directory that is not part of the public URL is just as incorrect.
5. Permit .htaccess overrides
Apache can ignore a perfectly written file when the virtual-host or directory configuration disallows overrides. The YOURLS FAQ specifically identifies AllowOverride All as the setting to check. Confirm that the relevant <Directory> block permits overrides for the YOURLS document root and that no more-specific block disables them. On managed hosting, this may require a provider change rather than an edit to the file itself.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
6. Check ownership and filesystem permissions
If YOURLS could not create its .htaccess automatically, inspect whether the web-server user can read the directory and file and whether the deployment process placed the file in the active document root. Permission errors may appear in the error log even when the browser shows only a generic 404. Correct ownership and readable permissions using your host’s documented method, then verify that the file is not hidden by a deployment rule or ignored during upload.
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.
Fixing an Nginx installation
Nginx does not read Apache .htaccess files. Its equivalent routing must be in the active server block, and PHP requests must be passed to PHP-FPM. Putting a correct Apache file on an Nginx host has no effect.
Root-domain configuration
In the Nginx location / block, use the documented fallback pattern:
try_files $uri $uri/ /yourls-loader.php$is_args$args;Nginx first serves an existing file or directory. For a short slug that is neither, it internally routes the request to /yourls-loader.php while preserving the query string through $is_args$args. The PHP location must then pass that script to PHP-FPM, using the socket or address configured for your server.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Subdirectory configuration
For YOURLS installed under a public path such as /subdir/, use the corresponding fallback inside that location:
try_files $uri $uri/ /subdir/yourls-loader.php$is_args$args;The subdirectory in the fallback must match the URL path and the filesystem layout. A fallback to /yourls-loader.php on a subdirectory install bypasses the intended application; a fallback with a duplicated directory sends Nginx to a path that does not exist.
Confirm the PHP-FPM hand-off
After Nginx selects yourls-loader.php, the request still needs to reach PHP-FPM. Check the PHP location, script filename mapping, socket or upstream address, and PHP-FPM logs. If Nginx can serve static files but the loader returns an upstream error or another 404, the rewrite is working and the PHP hand-off is the next boundary to inspect. Nginx server-block changes must be accepted by the service and reloaded using your operating system or hosting provider’s procedure.
Match the rule to the installation layout
| Deployment | Rewrite mechanism | Base or location | Loader target | Frequent mistake |
|---|---|---|---|---|
| Apache at domain root | .htaccess with mod_rewrite |
RewriteBase / |
/yourls-loader.php |
Overrides disabled or another application’s rules in the same file |
Apache in /somedir/ |
.htaccess with mod_rewrite |
RewriteBase /somedir/ |
/somedir/yourls-loader.php |
Using root paths that omit /somedir/ |
| Nginx at domain root | try_files in the active server block |
location / |
/yourls-loader.php$is_args$args |
Expecting Nginx to read .htaccess |
Nginx in /subdir/ |
try_files in the matching location |
Location that serves /subdir/ |
/subdir/yourls-loader.php$is_args$args |
Fallback points to the wrong directory or PHP-FPM is not connected |
The table is a path check, not a universal server template. The official server documentation notes that configuration differs between installations and that Nginx operators must adapt the pattern to their own needs.
Resolve conflicts with other applications and proxies
Separate rewrite owners
A rewrite-driven application installed in the same root directory can claim a YOURLS slug before YOURLS sees it. The official guidance names WordPress as an example and says the YOURLS root .htaccess should contain YOURLS directives only. The cleanest arrangement is a dedicated short-link domain. If that is not possible, isolate YOURLS in its own subdirectory and make every base and loader path include that directory.
Check the proxy or CDN layer
If a reverse proxy sits in front of Apache or Nginx, verify which origin receives the request and whether the proxy has a separate route for the short-link host. Compare the proxy access log with the origin access log for the same timestamp. A proxy-level 404 means changing YOURLS rules on the origin will not help until the proxy forwards that path.
Check host and scheme consistency
Make sure the short URL uses the hostname and scheme served by the virtual host where YOURLS is installed. Redirects between HTTP and HTTPS or between alternate hostnames can select a different server block with a different document root. Correct the canonical host or duplicate the required routing in the block that actually receives the request.
Use symptoms to choose the next check
| Observed result | Most useful next check |
|---|---|
| Admin page and static files load, every short slug is 404 | Verify mod_rewrite, .htaccess overrides, or the Nginx try_files fallback. |
Apache host ignores edits to .htaccess |
Confirm the active document root and AllowOverride All in the matching directory configuration. |
| Nginx serves files but the loader is never reached | Inspect the location block and ensure the fallback points to the correct root or subdirectory path. |
| Only a subdirectory installation fails | Compare the public URL, RewriteBase or location path, and loader target character for character. |
| The response is branded as another application | Remove competing rewrite rules from the YOURLS root or isolate the applications on separate roots. |
| The origin logs show no request | Investigate DNS, the proxy, load balancer, or the wrong virtual host before changing YOURLS files. |
| The loader is reached but PHP reports an upstream failure | Check PHP-FPM connectivity, script filename mapping, and the PHP-FPM log rather than rewriting the slug rule. |
Verify the repair safely
- Save a backup copy of the active virtual-host configuration and YOURLS
.htaccessbefore editing. - Make one focused change: enable the rewrite module, correct the base path, permit overrides, or adjust the Nginx fallback. Changing several layers at once makes the next log entry hard to interpret.
- Validate the server configuration using the normal Apache or Nginx configuration-check procedure for your operating system or host, then reload the service if required.
- Request one known-good short URL and watch the access and error logs at the same time.
- Confirm that the response is a redirect to the stored destination, not merely a 200 response from an error page.
- Retest from a second browser or a private window, then test another slug to rule out a cached result or a single-record issue.
If the 404 remains, capture the exact short URL path, response headers, web-server type and version, installation root or subdirectory, active rewrite configuration, and matching log lines. Those details are what a host administrator needs to identify a faulty virtual-host line or permission boundary; a generic YOURLS reinstall rarely addresses the underlying routing problem.
Choosing an environment that makes future fixes possible
For a new deployment, select an environment based on who can edit routing and inspect logs, not on a claim that one server is universally better. Apache is convenient when your host supports a YOURLS-specific .htaccess and grants the required overrides. Nginx is equally suitable when you can edit the server block and maintain PHP-FPM. A managed plan that hides both rewrite configuration and logs can make even a simple 404 difficult to diagnose.
| Decision factor | Apache | Nginx |
|---|---|---|
| Rewrite model | mod_rewrite plus YOURLS .htaccess |
try_files in the server configuration |
| Root versus subdirectory | Change RewriteBase and loader path |
Change the location and fallback path |
| Configuration access | Needs permitted overrides or virtual-host access | Needs server-block access; .htaccess is ignored |
| PHP integration | Depends on the host’s PHP handler | Requires a working PHP-FPM location and upstream |
| Diagnostics | Access to Apache access and error logs | Access to Nginx and PHP-FPM logs |
When documentation cannot identify the exact faulty line
The official YOURLS server documentation cautions that configuration differs from one installation to another. That is why two sites can use the same YOURLS release and require different virtual-host blocks, proxy settings, or permissions. If you have confirmed the symptom, matched the root or subdirectory paths, kept YOURLS’ rules separate, and still receive a 404, the remaining answer is in the active server configuration and logs. Provide those artifacts to the person who controls the host instead of guessing at additional rewrite directives.
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.
