Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1193
  • Last Modified:

Apache cert

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
atorex
Asked:
atorex
  • 7
  • 5
  • 3
1 Solution
 
cristiantmCommented:
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
 
atorexAuthor Commented:
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
 
GaryCommented:
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
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
cristiantmCommented:
If this that cathal mentions is not the case, could you post the main parts of your vhost config?
0
 
atorexAuthor Commented:
I have  the below in the httpd-ssl.conf


<VirtualHost _default_:443>
0
 
GaryCommented:
And the rest of it...
0
 
atorexAuthor Commented:
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
 
cristiantmCommented:
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
 
atorexAuthor Commented:
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
 
GaryCommented:
Looks like cristiantm has hit the nail on the head
0
 
atorexAuthor Commented:
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
 
cristiantmCommented:
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
 
atorexAuthor Commented:
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
 
cristiantmCommented:
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
 
atorexAuthor Commented:
Thanks, we are getting some self signed certs.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 7
  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now