The short answer is when you receive the message “the specified url cannot be found,” it means that your request to the application on the server or application itself was not able to be located by the server or application. It’s a 404-type error. The typical causes are incorrect or outdated URL, lost or relocated file, or server configuration issue – suspect server configuration, file, URL.
Choose a topic based on the book.Select a subject from the book.
What “The Specified URL Cannot Be Found” Means
A 404 response means the client was able to communicate with the server, but the server couldn’t find what was requested, or isn’t configured to fulfill the request. It’s not a failure by the DNS that prevents the server from being reached (IP unreachable). There is a difference between the two cases “Cannot find server” or “DNS Error” and “HTTP 404 – File not found” on one IIS troubleshooting page.
I was unable to find any product that exactly to verify this word for word. Message: Messages similar to this are displayed in the Windows and IIS-type error pages, as well as other Web applications, and the core processing identical. Use the procedure below as a general approach.
The 404 Diagnosis Ladder
The 404 Diagnosis Ladder (Original Framework) is a basic guide for site owners and administrators to use when designing their sites.
Do these steps as a sequence. Make sure to stop on finding cause. This is an editorial procedure and not the official Microsoft procedure.
- Check the URL. The most prevalent reason is a misspelled or old address. Look for typos, missing characters, wrong capitalization on case-sensitive servers and trailing slashes.
- Remove the browser. Try to refresh the page, use another browser/device and clear cached data. 404s can also be temporary issues as a result of glitches.
- Check the page is already available. Is the file or post still there at that location? It has been moved, renamed or unpublished?
- Check server configuration. Look at handlers, extensions, rewrites and permalinks.
- Read the logs. Server logs provide information on the requested URL and the status returned, and therefore on the pattern to correct, not the page.
Where the Fault Typically Lies
| Symptom | Likely cause | First fix |
| No symptoms | Safe channels most likely have congestion | 8-14 growth nodes |
| The latter is where a single page is failing, but another is operating and either the page has been removed or it has been renamed or the link has been mistakenly typed. | ||
| Failure of every inner page – Home page OK | rewrite/permalink problem | Resave permalinks or check rewrite rules |
| All the dynamic pages are broken (ASP, ASP.NET dynamic pages).(Apache rewrite mod, PHP, NET) | Extension is not enabled on server | Enable the extension on the server. |
| Static file has an exceptional extension | Extension not in the MIME map | Add the MIME type |
| Failures started from a migration or redesign, when some URLs were changed, use 301 redirects in order to map old to new URLs. |
IIS Server-Side Causes
It identifies certain specific causes of the problem on a Microsoft IIS server.
- The specified file is missing or out of position. Confirm that the file requested is in the proper location and exists where IIS expects it to be. Determine using IIS Manager which folder a particular URL is mapped to.
- There’s no web extension checked on. If you are getting dynamic content, a 404.2 will mean that the web extension is not enabled in the W3C extended log.
- Extension is not mapped. In the case of static content, a 404.3 will imply that the extension is not associated with a recognized MIME type in the MIME map.
- Dynamic content when installed as a default IIS 6.0. Out of the box, IIS on Windows Server 2003 displays only static information; ASP.After that, NET,ASP, CGI or ISapi content will return 404, unless you enable the desired web service extension.
- ASP.NET isn’t installed. In one SonicWall instance, a 404 was returned even with framework folders, due to ASP.NET was not each and every bit set up.
Most of this guidance was for previous versions of IIS, so see your correlating setup in the version of IIS you are using.
Fixes for Website Owners
If the error appears on your own website treat as a technical and SEO issue.
- In WordPress go to Settings, Permalinks and resave it, without changing anything. This is to refresh the Rewrite rules.
- Client migration or website redesign – 301 redirect old URLs to the new ones.
- Fix internal links. When links lead to non-existent content, visitors will run into a 404.
- Implement a 404 page. With IIS you can configure it to show a custom error page which would provide some navigation support for the visitors instead of just an error. You can also log or send by e-mail you’re requested URL to discover the damaged links.
- Use Search Console’s monitor. Check pages report for not found URLs and determine which should be redirected.
Not all 404 errors require a solution. A 404 can be a valid indication that the resource will be available some day in the future, or it was intentionally removed.
Troubleshooting Checklist
A checklist for troubleshooting with students.
- Verified that the URL contains no typos, change case and trailing slash
- Used other browser/device
- Removed the browser’s cache and cookies.
- Confirmed that there is a page or file at that path.
- Determined if the page had been moved, renamed or unpublished
- Re-generated permalinks (WordPress) or Rewrite rules (apache)
- Name of extensions, handlers and MIME types that are confirmed to work with IIS
- Looked at the server logs to determine the specific request
- Added 301 redirects for modified URL’s
- Create an informative 404 page
Guest Post Angles
For these topics, they are appropriate for web hosting, WordPress and SEO publications:
- How search engines deal with 404 vs 410 vs soft 404.
- A checklist to help you with redirecting websites to new locations.
- Identifying internal links with logs and Search Console.
First Solve the Problem, Then Build a Safety Net
If the next time you get the page – The specified URL cannot be found – then don’t refresh it repeatedly. Follow the ladder, determine the issue – Address, File, and/or Server – fix which ever applies. Finally, integrate a redirect and a valuable custom 404 page, so that the same mistake doesn’t cost your visitors dear the next time.
