Apache crashes with the following error
[ssl:warn] [pid 6056:tid 408] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
when executing php script that send emails using Swiftmailer on localhost.
How to solve this issue ?
details: XAMPP v3.2.1 with PHP 5.6 , windows 8.1
asked May 19, 2015 at 12:48
3
In case this helps, I was getting the same error because I have docker started. The trick is to stop it and start apache first.
answered Jul 27, 2018 at 19:50
1
Not the answer you're looking for? Browse other questions tagged php apache ssl xampp swiftmailer or ask your own question.
UFHH01
Guest
- #5
Hi toomanylogins, [Tue Aug 08 17:20:55.799794
2017] [ssl:warn] [pid 14805] AH01909: webmail.youdopet.com:443:0 server certificate does NOT include an ID which matches the server name [Tue Aug 08 17:20:55.856285 2017] [ssl:warn] [pid 14806] AH01909: webmail.youdopet.com:443:0 server certificate does NOT include an ID which matches the server name
[Tue Aug 08 17:20:55.800884 2017] [ssl:warn] [pid 14805] AH01909: lists:443:0 server certificate does NOT include an ID which matches the server name
[Tue Aug 08 17:20:55.801910 2017] [ssl:warn] [pid 14805] AH01909: default-192_168_1_20:443:0 server certificate does NOT include an ID which matches the server name
[Tue Aug 08 17:20:55.857292 2017] [ssl:warn] [pid 14806] AH01909: lists:443:0 server certificate does NOT include an ID which matches the server name
[Tue Aug 08 17:20:55.858950 2017] [ssl:warn] [pid 14806] AH01909:
default-192_168_1_20:443:0 server certificate does NOT include an ID which matches the server name
Pls. note as well the difference between WARNINGS, NOTICES and ERRORS, when you investigate issues/errors/problems.
You will solve that with correct certificates and their corresponding root certificates on domains and IPs.
Which leaves us now with:
[Tue Aug 08 17:20:55.803151 2017] [suexec:notice] [pid 14805] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
=> only a NOTICE - nothing more!
[Tue Aug 08 17:20:55.863152 2017] [mpm_prefork:notice] [pid 14806] AH00163: Apache/2.4.10 (Ubuntu) mod_fcgid/2.3.9 OpenSSL/1.0.1f configured -- resuming normal operations
[Tue Aug 08 17:20:55.863196 2017] [core:notice] [pid 14806] AH00094: Command line: '/usr/sbin/apache2'
... and again... ONLY a typical notice... nothing more!
Last edited by a moderator: Aug 8, 2017
Okay, I noticed that this post is viewed quite often recently and so it seems that a lot of people are facing the same issue that I did. If so then this might help you.
I have followed a simple step-by-step tutorial to create a SSL-certification for my webserver. Like so many tutorials out there the outcome of the tutorial I followed was a self-signed certificate using OpenSSL. Yep self-signed, that was the problem. The browser could not trust the server due to it's certificate which is signed by itself. Well I wouldn't do either...
A certificate has to be signed by an external trustworthy certificate authority (CA). So I stumbled upon Let's Encrypt which does all the work for you and is even easier to set up and the best is: it is absolutely free.
Installation
1) Delete your old ssl cert files which you have created by using OpenSSL
2) Open backports to get certbot client on Debian. You should know that this will open a hole for unfinished software! Install only the packages when you are aware about what you are doing.
echo 'deb //ftp.debian.org/debian jessie-backports main' | sudo tee /etc/apt/sources.list.d/backports.list3) Update your linux system
sudo apt-get update4) Install certbot
sudo apt-get install python-certbot-apache -t jessie-backports5) Set up apache ServerName and ServerAlias
sudo nano /etc/apache2/sites-available/000-default.conf6) Edit apache config file
<VirtualHost *:80> . . . ServerName example.com ServerAlias www.example.com . . . </VirtualHost>7) Check for a correct syntax
sudo apache2ctl configtest8) If the config file looks fine, restart apache server
sudo systemctl restart apache29) Set up a certificate using certbot and follow the instruction on screen.
sudo certbot --apacheRenewal
All certificates by Let's Encrypt are valid through 3 months. To renew the you can manually run
sudo certbot renewOr automate this service as a cron job
sudo crontab -eand enter the following row to invoke a renewal every Monday at 2:30 am.
. . . 30 2 * * 1 /usr/bin/certbot renew >> /var/log/le-renew.logYou can follow a more detailled tutorial here: //www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-debian-8