grabby Posted February 10, 2012 Report Share Posted February 10, 2012 After I got a number of dev sites up including one with an ssl cert with Coral 8.0.0 as per Yoni’s advice in http://forum.uniformserver.com/index.php?showtopic=2467 I decided to upgrade to 8.1.1. Everything was fine until I went to the site with the certificate, which caused Apache to crash with the message Apache HTTP Server has encountered a problem and needs to close. We are sorry for the inconvenience. Of course I had generated a new certificate in 8.1.1. The content of the error message started with AppName: httpd1.exe AppVer: 2.2.22.0 ModName: php5ts.dllModVer: 5.3.10.0 Offset: 000a3b02 Clicking on “more information” after reporting the error took me to http://wer.microsoft.com/responses/Respons...b9-4d3b4c938009 which states PHP Script Interpreter has stopped working properly. Meanwhile, the Apache syntax checks OK. The only other difference from my 8.0.0 installation is that instead of leaving UniServer in its directory so that my sites ended up in, say C:\UniServer\vhosts\mysite1C:\UniServer\vhosts\mysite2 etc. I put it straight into the top of the drive since I don’t have anything else there, so the sites end up in C:\vhosts\mysite1C:\vhosts\mysite2 etc. Any idea what’s going on? Quote Link to comment Share on other sites More sharing options...
Yoni Posted February 10, 2012 Report Share Posted February 10, 2012 I think you want to go back to C:\UniServer\.... That's what causing the issue I believe. You have broken paths by removing "UniServer" Quote <p class="bbc_center"><span style="font-size:12px;"><strong>Yoni</strong></span></p> Link to comment Share on other sites More sharing options...
grabby Posted February 10, 2012 Author Report Share Posted February 10, 2012 Hi Yoni, Thanks for the quick reply. I don’t think it’s a path issue because my other sites all work fine, it’s only the one with the ssl that causes this. To make sure I put everything back in C:\UniServer\vhosts\mysite1C:\UniServer\vhosts\mysite2 etc. and adjusted everything accordingly, but the problem didn’t go away! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.