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
DLP : Root Endpoint Coordinator (REPC) is stuck at pending status. Number of Views Availability of Passkey Feature in RSA Authenticator 4.5 for iOS and Android Number of Views ID Plus Plans - Legacy Number of Views Unable to remove a Role Membership Rule from a Role in RSA Identity Governance & Lifecycle Number of Views How to check the TTLS ( LDAPS /ODA )certificate from the packet capture Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
