- #Xampp apache service detected with wrong path Patch#
- #Xampp apache service detected with wrong path windows#
So clear your error.log file (zero it out). log seems incomplete, as last line shows a child process starting, then additional error logged related to a crash. So it's unlikely you're hitting any Apache bug.ģ) The file C:\xampp\apache\logs\error.
#Xampp apache service detected with wrong path Patch#
Remove certs from any consideration of this problem + best leave certs commented out till you fix the real problem.Ģ) You're running Apache/2.4.51 which is very good, so you're running latest Apache with almost every patch applied. I wouldn't expect for commenting these lines out to have any effect. seen on almost every Apache instance, independent of OS. Since the SSL log entries you mentioned are warnings. Does that sound as a valid path or is there a better/easier way?ġ) The most important question is if Apache started when you commented out the SSL lines.
#Xampp apache service detected with wrong path windows#
Also, I think I need to delete the Apache folder and start from a vanilla one and see whether it starts a Windows service and then add my virtual hosts and other config changes I applied on 2016, one by one, to see where it fails. I guess I need to make it log everting in a debug mode or something. As I mentioned initially, after commenting out SSL related stuff in nf, Apache still doesn't run, but it doesn't give any error messages either, so I am not sure what's wrong. I would be content with applying the cert on 2019 after I make the site up and running w/o SSL enabled, but I need to make the Apache start on 2019 in the first place and I have trouble with that (and not much in the logs). The idea is to try and copy that website to Win 2019, but I see what you mean by them not going going to be able to be accessible at the same time.
The cert was configured for the "" site running on Win 2016. In order to troubleshoot, it would be nice to enable logging, but I am not sure where to start. AH00455: Apache/2.4.51 (Win64) OpenSSL/1.1.1l PHP/8.0.12 configured - resuming normal operations AH00456: Apache Lounge VS16 Server built: 16:27:02 AH00094: Command line: 'c:\\xampp\\apache\\bin\\httpd.exe -d C:/xampp/apache' AH00418: Parent: Created child process 7852 AH01909: server certificate does NOT include an ID which matches the server name AH00354: Child: Starting 150 worker threads.īut then I commented out all the lines related to SSL and now I don't see any errors in Apache's error.log and in C:\xampp\php\logs\php_error_log. AH01909: server certificate does NOT include an ID which matches the server name
3:59:01 PM Press the Logs button to view error logs and check 3:59:01 PM the Windows Event Viewer for more clues 3:59:01 PM If you need more help, copy and post this 3:59:01 PM entire log window on the forumsĪt some point, after trying to start the Apache2.4 service, I saw this in C:\xampp\apache\logs\error.log: 3:59:01 PM This may be due to a blocked port, missing dependencies, 3:59:01 PM improper privileges, a crash, or a shutdown by another method. 3:59:00 PM Status change detected: running 3:59:01 PM Status change detected: stopped 3:59:01 PM Error: Apache shutdown unexpectedly. Here is what XAMPP Control Panel message says:ģ:58:19 PM Attempting to start Apache service.ģ:58:59 PM Attempting to start Apache service.
I added Apache2.4 to the list of Windows services, but it doesn't want to start. After moving the htdocs folder, as well as the SSL certificate related files (*.crts), I also copied some lines I edited on the old machine to C:\xampp\apache\con\nf on the new server. I am using XAMPP, which works fine on the 2016 VM. I am moving a webserver from Windows Server 2016 to Windows Server 2019.
0 kommentar(er)
