Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

Installing SilverStripe /

Getting SilverStripe up and running on your computer and on your web server.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Migration of Silverstripe from Apache to IIS

Go to End

4 Posts   2052 Views


Community Member, 2 Posts

4 February 2010 at 4:26am


I have had to migrate silverstripe from apache to IIS, everything has been copied fine including the database. I had issues with the mod_rewrite stuff in the htaccess file but managed to get around that issue successfully (i think)

However now when you load the root folder it directs to a 404 error page. ie when i go to it 404 errors but if I go to it is fine. I have set IIS to use index.php as the default file however it still does not work.

I then decided to make my own index.php and see if that was loading... which it was, so this leads me to believe that the index.php file is loading however something within silverstripe is redirecting to a 404.

Does anyone know how to resolve this issue?

Any help on this matter is much appreciated.



Community Member, 712 Posts

5 February 2010 at 7:53am

SilverStripe's index.php exists purely to allow it to work without mod_rewrite. If your rewriting rules are working you should be able to delete it.

I don't know how IIS handles rewrites, but that's where your error is.


Forum Moderator, 922 Posts

7 February 2010 at 2:09pm

Edited: 07/02/2010 2:13pm

Which version of IIS are you migrating to?

IIS 7 and 7.5 use this extension for rewriting: Create a new web.config file in your project and add the following from this page:

If using IIS 5 or 6 it may be a little more difficult, as there are no official rewriting extensions for these versions. However, there are third-party extensions that may work.



Community Member, 2 Posts

5 May 2010 at 8:12pm

Thank you for the replies. However i thought i would update you guys and let you both know that we are migrating back to a LAMP server, so the problem will resolve itself.

Many thanks