Recommended Free Tools
If index.html is uploaded but your new site still shows a welcome page, a blank response, 404, 403, or a directory listing, the file is usually not being selected by the site that answered your request. The usual causes are a wrong document root, the wrong virtual host or hostname, a missing default-document rule, a capitalization mismatch, or permissions that prevent the web-server account from reading the file.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Test /index.html first, then test /. That one comparison tells you whether the problem is direct file lookup or directory-index selection.
As an Amazon Associate I earn from qualifying purchases.
Start with the fastest test: request the file directly
- Open
https://your-hostname.example/index.html(or the equivalent HTTP URL). - Open
https://your-hostname.example/. - Record the exact result for each request: your page, an old welcome page, 404 Not Found, 403 Forbidden, or a directory listing.
If /index.html works while / does not, the file is reachable and the fault is almost certainly the directory-index or default-document configuration. If both fail, check the active site, filesystem path, filename, and permissions before changing index settings.
What should happen when someone visits the root URL
A request for / names a directory, not a file. The server maps that URL to a filesystem directory and then chooses a default document from an ordered list. Apache calls the setting DirectoryIndex; NGINX uses the index directive; IIS uses an enabled, ordered Default Document list.
Apache’s documented example maps DocumentRoot /var/www/html to the URL root. When a directory is requested, Apache can serve /var/www/html/index.html if DirectoryIndex index.html is enabled. NGINX maps a URI through its configured root or alias and uses the filenames in its index directive, which defaults to index.html. IIS checks its default-document list and returns the first filename it finds; Microsoft lists Index.html among the standard entries.
That means uploading a file named index.html is not, by itself, a guarantee that / will display it. The request must reach the intended site, map into the directory containing the file, and pass the server’s default-document and access checks.
Free tools Windows power users keep installed
One-click scans. No signup required.
Diagnose the failure layer by layer
1. Confirm the active document root
The folder used by your file-transfer tool is not necessarily the folder the web server publishes. Find the path configured for the site that answered the request.
| Server | Path setting to inspect | What must be true |
|---|---|---|
| Apache | DocumentRoot |
index.html is inside that directory (or the requested subdirectory). |
| NGINX | root or alias |
The URI-to-filesystem mapping resolves to the directory containing the file. |
| IIS | Site physical path | The file exists beneath the physical path of the selected IIS site. |
Check the actual server configuration, not just a control-panel label. A common mistake is uploading to a home directory, deployment directory, or old site folder while the active site points somewhere else. Put a temporary, uniquely named text file in the suspected directory and request that filename directly. If it cannot be fetched, you are probably inspecting the wrong root or the wrong site.
2. Verify the hostname and selected site
A hostname can reach the wrong machine or the wrong virtual host even when your files are perfect. DNS must resolve the hostname to the server’s IP address, and the request’s Host value must match the intended Apache virtual host, NGINX server block, or IIS site binding.
Seeing a provider’s welcome page, an older project, or another person’s site usually indicates site selection rather than an HTML problem. Apache’s documentation explicitly notes that creating virtual-host configurations does not create DNS records. Confirm the DNS record, the server IP, and the hostname binding. Test the hostname, not only the numeric IP: an IP request may select a different default site because it carries a different host value.
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 →Repair Windows errors before they cause bigger problemsFix Now →3. Check the filename and every directory name exactly
Use the exact spelling index.html. Check for Index.html, index.HTML, trailing spaces, duplicate extensions such as index.html.html, and an upload that landed in a similarly named directory. Apache request paths are case-sensitive, and many Unix filesystems are case-sensitive as well. A capitalization mismatch can therefore produce a missing-file response even when the names look equivalent on a case-insensitive desktop.
Match the URL path as well as the filename. A file at /public/index.html is not the same resource as /index.html unless the server configuration maps those paths together.
4. Check default-document settings
When direct lookup succeeds but the root URL fails, inspect the relevant setting.
- Apache: ensure the active directory context enables
DirectoryIndex index.html. If several names are listed, order matters: an earlier existing file can be served instead of yours. - NGINX: ensure the applicable server or location block has an
indexdirective that includesindex.html. A more specific location block can override a setting you changed elsewhere. - IIS: enable the Default Document feature and place
Index.html(or the exact filename you use) in the list. IIS returns the first listed file it finds, so an earlier welcome document can win.
After changing configuration, reload or restart the service using your operating system’s normal service-management method, then test again. If a configuration test reports a syntax error, fix that error before reloading; an unchanged running configuration can make a correct-looking edit appear ineffective.
5. Check read and traverse permissions
The web-server account needs permission to read the file and to traverse every parent directory. Apache’s documentation gives 644 for ordinary files and 755 for directories as typical Unix examples, subject to the account model and local security policy. Those numbers are not a universal requirement: ownership, group membership, access-control lists, and mandatory security controls can change the result.
Inspect the complete path, not only the final file. A directory with no execute (traverse) permission can block access to a readable file inside it. Avoid solving a 403 by making the entire tree world-writable; grant the server account the least access it needs and preserve the permissions required by your deployment process.
6. Read the server logs and classify the status
Logs distinguish path errors from access errors and often identify the exact filesystem path being tested. Check the access log and error log at the time of a fresh request, then correlate the status code with the symptom:
| Observed result | Most likely layer | Next check |
|---|---|---|
| Old or generic welcome page | DNS or virtual-host/server-block selection | Hostname resolution, site bindings, and the active root for the site that answered. |
/index.html works; / fails |
Default-document selection | Apache DirectoryIndex, NGINX index, or IIS Default Document order. |
| 404 Not Found | Path mapping or filename | Document root, root/alias, physical path, and capitalization. |
| 403 Forbidden | Access rules or filesystem permissions | Parent-directory traversal, file readability, server restrictions, and error-log details. |
| IIS 403.14 | No default document while directory browsing is disabled | Add or enable the intended default document; do not rely on directory listing. |
| Directory listing | Directory indexing enabled without a selected default | Configure the intended index file and disable listing unless it is deliberately required. |
Apache identifies filesystem permission failures as a common source of Forbidden responses. IIS documents 403.14 for a directory with no available default document when browsing is disabled. Treat those messages as clues about the failing layer, not as evidence that the HTML itself is malformed.
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 errorsServer-specific checklists
Apache
- Identify the virtual host handling the hostname and read its
DocumentRoot. - Confirm the file exists below that directory with the exact case
index.html. - Check that the relevant directory configuration includes
DirectoryIndex index.htmland that no earlier default file is taking precedence. - Verify the Apache account can traverse each parent directory and read the file;
644files and755directories are common starting points, not blanket rules. - Review the error log for permission, override, or path-mapping messages, then reload after a validated configuration change.
NGINX
- Find the server block selected by the hostname and inspect its
rootoralias. - Resolve the requested URI to the actual filesystem path and verify that
index.htmlis there. - Check the effective
indexdirective in the matching location; a nested location can override a server-level value. - Confirm filesystem permissions for the NGINX worker account and inspect the error log for access or “file not found” details.
- Validate the configuration before reloading, then retest both
/index.htmland/.
IIS
- Open the IIS site configuration and confirm its physical path and hostname binding.
- Verify the file exists there with the exact spelling and capitalization used by the default-document entry.
- In the Default Document feature, ensure the desired entry is enabled and ordered ahead of unwanted welcome files.
- Check NTFS permissions for the application-pool identity or account serving the site.
- Use the IIS status code and logs to distinguish a missing file, binding mismatch, permission denial, and 403.14.
Why common “fixes” do not work
Uploading another copy of the file
A second upload does nothing when DNS selects another server or the site points at another root. Prove the path with a direct request and a uniquely named test file before uploading again.
Renaming only the local copy
Renaming Index.html to index.html on your computer is insufficient if the remote file remains unchanged, if the transfer tool altered the name, or if the URL reaches a different directory. Inspect the remote listing or filesystem directly.
Enabling directory browsing
A listing can hide a missing default-document rule and expose filenames. Configure the intended index file instead. Directory browsing is not a substitute for a homepage and should remain disabled unless you have a deliberate reason to publish listings.
Changing permissions to 777
Overly broad permissions can create a security problem while masking ownership or path issues. Determine which account serves the site, grant read and traverse access through the path, and keep write access limited.
A repeatable troubleshooting sequence
- Request
/index.htmland/; write down both status codes and page content. - Confirm DNS resolves the hostname to the intended server IP.
- Confirm the selected virtual host, server block, or IIS binding matches that hostname.
- Read the active document root or physical path from the server configuration.
- Verify the exact remote path and capitalization of
index.html. - If direct lookup works, correct default-document configuration and its ordering.
- If the response is 403, check server rules plus read and traverse permissions.
- Review logs after each change, reload validated configuration, and retest from a fresh browser session.
This sequence prevents you from changing several layers at once. The first test that fails identifies the layer that needs repair.
When the page is fixed but the browser still shows the old result
If the server logs show your request reaching the correct site and returning the new file, a browser cache, intermediary cache, or service worker can preserve older content. Verify with a private window and an HTTP client request, then inspect response headers and the application’s caching rules. Do not use cache-clearing as a substitute for checking the server path: it cannot make a file reachable when the wrong site or root is answering.
FAQ
Why does /index.html work but the homepage URL does not?
The file lookup succeeds, but the directory request is not selecting it. Add or correct the Apache DirectoryIndex, NGINX index, or IIS Default Document entry, and check whether an earlier file is taking priority.
What does a 404 usually mean on a new server?
The active site’s path mapping does not resolve to the requested file, or the URL and filename capitalization differ. Verify the selected site, document root or physical path, and exact remote filename.
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 →Why am I seeing a provider welcome page instead of my upload?
The hostname may resolve to another server, or the request may be selecting a different virtual host, server block, or IIS binding. Check DNS, the hostname binding, and the configuration of the site that actually answered.
Is 644 for files and 755 for directories always correct?
No. Apache documents those as typical Unix examples. The correct permissions depend on ownership, groups, access-control lists, mandatory security policy, and the identity used by the web server. The requirement is effective read access to the file and traverse access through every parent directory.
Frequently Asked Questions
Can an uppercase filename work on one server but fail on another?
Yes. Filesystems and URL handling differ. A path that treats Index.html and index.html as distinct will return a missing-file result when the case does not match exactly.
What should I check if a directory listing appears?
The server found the directory but did not select a default document. Configure the intended index file and disable directory browsing unless listing is an intentional feature.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
