Solved

Apache cert

Posted on 2014-01-13
15
1,120 Views
Last Modified: 2014-01-14
Im getting the below error on my Apache error.log, we have a wildcard Cert and am not sure if that is the issue. Could anyone help tracking the cause and resolution for this issue?

[Mon Jan 13 08:53:35.083158 2014] [ssl:warn] [pid 1308:tid 400] AH01909: RSA certificate configured for APP03a:443 does NOT include an ID which matches the server name
[Mon Jan 13 08:53:35.661285 2014] [ssl:warn] [pid 1308:tid 400] AH01909: RSA certificate configured for APP03a:443 does NOT include an ID which matches the server name
[Mon Jan 13 08:53:35.661285 2014] [mpm_winnt:notice] [pid 1308:tid 400] AH00455: Apache/2.4.2 (Win32) OpenSSL/1.0.1 configured -- resuming normal operations
[Mon Jan 13 08:53:35.661285 2014] [mpm_winnt:notice] [pid 1308:tid 400] AH00456: Server built: May 11 2012 16:55:33


regards,
0
Comment
Question by:atorex
  • 7
  • 5
  • 3
15 Comments
 
LVL 3

Expert Comment

by:cristiantm
ID: 39777135
The certificate is issued for a wildcard domain (*.something.com), but your vhost is not on that domain (APP03a), thats why the *warning* (not error) appears.
0
 

Author Comment

by:atorex
ID: 39777189
Thanks for the reply,
there is an application that connects to it, using the FQDN URL to it, I'm getting an ssl handshake error that made me think was due to this error.

the error from the Application,

08:48:55.168:WARN:oeji.nio:java.io.IOException: An established connection was aborted by the software in your host machine
INFO   | jvm 1    | 2014/01/13 08:50:08 | javax.net.ssl.SSLProtocolException: handshake alert:  unrecognized_name
0
 
LVL 58

Expert Comment

by:Gary
ID: 39777195
Do you have something like this

<VirtualHost 127.0.0.1:443>
ServerName www.domain.com:443


If so remove the :443 from the ServerName line
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 3

Expert Comment

by:cristiantm
ID: 39777221
If this that cathal mentions is not the case, could you post the main parts of your vhost config?
0
 

Author Comment

by:atorex
ID: 39777236
I have  the below in the httpd-ssl.conf


<VirtualHost _default_:443>
0
 
LVL 58

Expert Comment

by:Gary
ID: 39777281
And the rest of it...
0
 

Author Comment

by:atorex
ID: 39777285
Sorry here it is


<VirtualHost _default_:443>

#   General setup for the virtual host
DocumentRoot "/Apache24/htdocs"
ServerName https://app03a.globoalwork.com
ServerAdmin admin@example.com
ErrorLog "/Apache24/logs/error.log"
TransferLog "/Apache24/logs/access.log"

#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
SSLEngine on
0
 
LVL 3

Accepted Solution

by:
cristiantm earned 500 total points
ID: 39777326
Is your wildcard cert issued for *.globoalwork.com??

By the way, is it really globoalwork.com ? Not globolwork.com or globalwork.com ? ;) would be a very common mistake, and looks like this is the problem since I can see that globoalwork.com is an unregistered domain. So I think you just have a typo there.
0
 

Author Comment

by:atorex
ID: 39777343
yes its *.globalwork.com fat fingered it, and that is what the cert was issued to.

I may have an idea why this is having issues, the server's fqdn is app03a.globalHQ.com
when the admin created the server that's the Domain they put it in!
0
 
LVL 58

Expert Comment

by:Gary
ID: 39777349
Looks like cristiantm has hit the nail on the head
0
 

Author Comment

by:atorex
ID: 39777382
I corrected the fat finger error but still the same issue, that didn't resolve the issue, could this FQDN be the issue?
app03a.globalHQ.com
0
 
LVL 3

Expert Comment

by:cristiantm
ID: 39777389
You say the domain for the site is app03a.globalHQ.com? then you need a cert for app03a.globalHQ.com (or wildcard cert for *.globalHQ.com) and to setup the apache vhost name to app03a.globalHQ.com.
0
 

Author Comment

by:atorex
ID: 39777421
OK so that's likely the issue, the HQ domain is an internal domain so The server boys will have to move the server to the correct domain.
0
 
LVL 3

Expert Comment

by:cristiantm
ID: 39779141
Yes, that is correct. The SSL certificate Common Name will need to match the domain. If the site is in this domain just for testing/development, then you can use a self-signed (or in-house PKI) certificate for testing only.
0
 

Author Comment

by:atorex
ID: 39779204
Thanks, we are getting some self signed certs.
0

Featured Post

Secure Your Active Directory - April 20, 2017

Active Directory plays a critical role in your company’s IT infrastructure and keeping it secure in today’s hacker-infested world is a must.
Microsoft published 300+ pages of guidance, but who has the time, money, and resources to implement? Register now to find an easier way.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As Wikipedia explains 'robots.txt' as -- the robot exclusion standard, also known as the Robots Exclusion Protocol or robots.txt protocol, is a convention to prevent cooperating web spiders and other web robots from accessing all or part of a websit…
If you are a web developer, you would be aware of the <iframe> tag in HTML. The <iframe> stands for inline frame and is used to embed another document within the current HTML document. The embedded document could be even another website.
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

679 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question