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 Which services on the EnVision appliance are not needed? 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 Latest SecurID App Release Update and FAQs Number of Views RSA Announces the Availability of RSA Identity Management and Governance 6.9.1 Patch 131 Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?
