With that being said, warnings still aren’t ideal because they indicate that something is wrong with your installation. In fact, it’s more of a warning than an actual error. It’s important to note that this notification is most likely not related to whatever initial issue that brought you to the error logs. You check the XAMPP logs for clues about this problem and find the “Server Certificate Does NOT Include an ID Which Matches the Server Name” message, often multiple times. The initial problem could involve crashing XAMPP components (usually Apache) or MySQL errors. Typically, what happens is that another issue brings you to the error log, and then you’ll notice the server certificate warning accidentally. Instead, you can find it in the XAMPP error logs: The “Server certificate does NOT include an ID which matches the server name” message. The elusive “Server certificate does NOT include an ID which matches the server name” error message doesn’t appear on the front end of a site. You can still run the control panel if you need to access things like to stop and start a service etc, but it is no longer necessary to have the control panel running all the time.An Introduction to the “Server Certificate Does NOT Include an ID Which Matches the Server Name” Warning in XAMPP Installing them as a service means you don’t need to run the control panel each time you want to work with your localhost as they will already be running. When both are installed as a service you will then see 2 green ticks. To install Apache and MySQL as a service simply click on the red cross for each and choose “Yes”. The solution is to install the modules eg Apache and MySQL to run as Services, as currently you would see a big red cross in the Service column of the control panel. The only problem with this solution, is every time you run the control panel, depending on your Windows settings, you will get a User Account Control warning message, confirming that you want to allow the program to make changes to your computer. You can overcome this by going to where XAMPP was install eg C:\xampp and right click on xampp-control.exe, choose Properties then go to the Compatibility tab and check the box next to “Run this program as an administrator” You are not running with administrator rights! This will work for most application stuff but whenever you do something with services there will be a security dialog or things will break! So think about running this application with administrator rights!Īn example of things breaking, is when you try to quit you may get the message every time.Įrror: Cannot create file “C:\xampp\xampp-control.ini”. If you try to run the XAMPP control panel after install you are likely to see in the console log a message that: In essence it is not so much an upgrade as it is a thorough backup, uninstall and reinstall of the new version. This is as much as anything a record for myself for next time I need to upgrade as to the things I have learnt. I am not going to cover every point in detail, if you need that I highly recommend reading the article. ![]() So I thought I would write this post to add my more recent experiences of the process, and reiterate some of the important points from the article. ![]() Trying to find a detailed explanation of how to upgrade for a Windows setup that works is difficult. ![]() Thanks to a really helpful article from WPMU DEV on How to Upgrade XAMPP for WordPress Without Losing Anything that I found 2 years ago, this process was far less time consuming than it could have been. What seem like shortcuts may just come back to bite you later. You need to take your time and backups can take a while. Upgrading XAMPP is a task to be undertaken when you are not under pressure by other work. ![]() With the latest major release of PHP, being PHP8 just recently released, I decided it was time for an upgrade to my local development environment.
0 Comments
Leave a Reply. |