<p>If I recall, IIS doesn't include <code>index.php</code> as a default document when looking for a page to load in a directory, but only things like <code>index.html</code>, <code>index.htm</code>, <code>deafult.html</code>, etc.</p>

<p><a href="https://technet.microsoft.com/en-us/library/cc771439%28v=ws.10%29.aspx" rel="nofollow">Here's how to change it.</a></p>

CC BY-SA 3.0
2015-05-22T19:43:13.383Z
I already added `index.php` to the default document list and it's first in the priority order.
Philip Jones
CC BY-SA 3.0
2015-05-22T19:53:40.800Z
Can you check the IIS error logs? Should have the underlying internal server error message there.
Brad Bell
CC BY-SA 3.0
2015-05-22T20:00:09.240Z
I don't think I have direct access to server logs. I'll have to check with the hosting provider to see if that's something I can get.
Philip Jones
CC BY-SA 3.0
2015-05-22T21:13:45.357Z
HTTP Error 500.19 - Internal Server Error  The requested page cannot be accessed because the related configuration data for the page is invalid.
Philip Jones
CC BY-SA 3.0
2015-05-22T21:20:14.383Z
I'm guessing IIS can't read the `web.config` file: https://stackoverflow.com/questions/9216158/the-requested-page-cannot-be-accessed-because-the-related-configuration-data-for and https://stackoverflow.com/questions/18620654/500-19-internal-server-error-the-requested-page-cannot-be-accessed-because-t and http://blogs.msdn.com/b/webtopics/archive/2010/03/08/troubleshooting-http-500-19-errors-in-iis-7.aspx
Brad Bell
CC BY-SA 3.0
2015-05-26T16:42:32.167Z
After a little work with the hosting provider, this has been resolved. It appears some of the statements in `web.config` were causing conflicts (either the `urlCompression` or `defaultDocument` sections). I removed those to no apparent ill effect, leaving only the rewrite. All is working for now. Thanks for the assist.
Philip Jones
CC BY-SA 3.0
2015-05-26T18:03:22.217Z
Glad you got it sorted, @PhilipJones.
Brad Bell
CC BY-SA 3.0
2015-05-22T19:37:14.530Z
2015-05-22T19:37:14.530Z
Brad Bell
<p>On a fresh install of <em>Craft</em> 2.3.2644, using the hostname alone, <code>example.com</code> returns an error, "<em>The page cannot be displayed because an internal server error has occurred</em>".</p>

<p>If I include <code>/index.php</code> (<code>example.com/index.php</code>), then the expected <code>index</code> template is returned, displaying the "Welcome to..." entry.</p>

<p>However, <code>example.com/news</code> returns the <code>news</code> template correctly, even without <code>index.php</code> in the URI.</p>

<ul>
<li>Craft 2.3.2644</li>
<li>Windows Server 2008 R2</li>
<li>IIS 7.5</li>
</ul>

<p>The <code>web.config</code> file included with the <em>Craft</em> install is present at web root.</p>

<p>What am I missing?</p>

<url><config><install><index>
Home page won't load without 'index.php'
# Home page won't load without 'index.php'

(Asked by: username_0 on 2015-05-22)

On a fresh install of *Craft* 2.3.2644, using the hostname alone, `example.com` returns an error, "*The page cannot be displayed because an internal server error has occurred*".

If I include `/index.php` (`example.com/index.php`), then the expected `index` template is returned, displaying the "Welcome to..." entry.

However, `example.com/news` returns the `news` template correctly, even without `index.php` in the URI.

* Craft 2.3.2644
* Windows Server 2008 R2
* IIS 7.5

The `web.config` file included with the *Craft* install is present at web root.

What am I missing?

**Tags:** url, config, install, index

---

## 1 answers

### Answer by username_1 on 2015-05-22. Score: 1

If I recall, IIS doesn't include `index.php` as a default document when looking for a page to load in a directory, but only things like `index.html`, `index.htm`, `deafult.html`, etc.

[Here's how to change it.](https://technet.microsoft.com/en-us/library/cc771439%28v=ws.10%29.aspx)

> **Comments:**
> **username_0**: I already added `index.php` to the default document list and it's first in the priority order.  
> **username_1**: Can you check the IIS error logs? Should have the underlying internal server error message there.  
> **username_0**: I don't think I have direct access to server logs. I'll have to check with the hosting provider to see if that's something I can get.  
> **username_0**: HTTP Error 500.19 - Internal Server Error  The requested page cannot be accessed because the related configuration data for the page is invalid.  
> **username_1**: I'm guessing IIS can't read the `web.config` file: https://stackoverflow.com/questions/9216158/the-requested-page-cannot-be-accessed-because-the-related-configuration-data-for and https://stackoverflow.com/questions/18620654/500-19-internal-server-error-the-requested-page-cannot-be-accessed-because-t and http://blogs.msdn.com/b/webtopics/archive/2010/03/08/troubleshooting-http-500-19-errors-in-iis-7.aspx  
> **username_0**: After a little work with the hosting provider, this has been resolved. It appears some of the statements in `web.config` were causing conflicts (either the `urlCompression` or `defaultDocument` sections). I removed those to no apparent ill effect, leaving only the rewrite. All is working for now. Thanks for the assist.  
> **username_1**: Glad you got it sorted, @PhilipJones.  

---

