I’m facing the same issue with IIS 8.5 so I’ve added these rewrite rules exactly as stated above but now when I run http://localhost:8000/ (i’m using 8000 port) it gives a “HTTP Error 404.20 - Not Found” and the browser URL turn into: http://localhost:8000/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/install/
I think it’s a rule issue, but I couldn’t trace which. Could you help me on that?
Thanks,
Beto
UPDATE:
I’ve removed the last rule and were able to complete the setup. After that I had the same 404.20 issue on login page. Thus I added the last rule back. I’m able to login but the Xibo pages are completely messy.
That would be because the resources cannot be loaded correctly, because the rules are wrong
Unfortunately no-one who has it working has been able to post the contents of their rules file - so I do not know if the above actually worked for them.
Perhaps you could follow the procedure they said worked?
Can you export the resulting rules so that we can pop them in our user manual?
That is strange - do other forms work? That message would imply that IIS isn’t configured for PHP correctly (which seems very odd) or that the rewrite rules are directing requests for that specific page to a different place.
We were able to get up and running on IIS using the same method.
After that, we ran into the same AJAX errors. It turns out they were caused by IIS rejecting the query string for being too long. We fixed this by changing the max query string in IIS. There are more details in this post:
I’m seeing this same issue. 405 errors when trying to apply a change on the settings page. The debug tools in Chrome say that the PUT method isn’t allowed which is weird because I swear I use PUT with other php pages/sites on this server.
I just tried to edit an existing user and got the same 405 error. When creating a user I don’t get an error because the method used is POST but when I try to edit an existing entry the PUT method is used and that is getting blocked.
Under 1.7.4 the method used for both creating and updating a user is POST.
Is this the way edits are intended to update in 1.8?
Thanks. It solved my problem. I made all directly from IIS Manager (just change to All verbs) as the screen shot. IIS needs double quota for save this settings. Please look for the Module line.
I am still having problems with receiving a 405 HTTP Verb error. I believe everything is done correctly with the HTTP Mapping in IIS, I don’t know if there’s a extra step I need to figure out with plesk? Any help would be much appreciated