Error 403 when trying to log in to RCM
Originally Published: 2009-11-13
Article Number
Applies To
Issue
Error 403 when trying to log in to RCM
admin-cipher.log shows:
[error] SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page (SSL-C library error follows)
[error] SSL-C: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request [Hint: speaking HTTP to HTTPS port!?]
admin-error.log shows:
[error] mod_ssl: SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page (SSL-C library error follows)
[error] SSL-C: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request [Hint: speaking HTTP to HTTPS port!?]
admin-access.log shows:
"GET /mod_ssl:error:HTTP-request HTTP/1.0" 403 305
"GET /mod_ssl:error:HTTP-request HTTP/1.0" 403 305
"GET /mod_ssl:error:HTTP-request HTTP/1.0" 403 305
Cause
Resolution
Look at the certificates in the browser. The admin certificate which will allow you to connect to the admin console is issued by "[your install name] Administrative CA" which is chained to "[your install name] System CA".
Related Articles
RSA Link Service Interruption: Availability of RSA SecurID Token Downloads Number of Views Latest SecurID App Release Update and FAQs Number of Views RSA Identity Governance and Lifecycle reports fail to send emails with error SMTPSendFailedException:552 5.3.4 Message siz… Number of Views Account and Group Resolutions fail when running a Data Entitlement Aggregate (DEA) Data Access Collector in RSA Identity G… Number of Views Account and Group Resolutions fail when running a Data Entitlement Aggregate (DEA) Data Access Collector in RSA Identity G… Number of Views
Don't see what you're looking for?
