Unable to access RSA SecurID Access Identity Router Console following initial deploy
Originally Published: 2019-09-24
Article Number
Applies To
RSA Product/Service: Identity Router
Issue
httpd2-worker: apr_sockaddr_info_get() failed for linux-rfng
httpd2-worker: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
httpd2-worker: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
Cause
Workaround
- Redeploy the VM.
- Disconnect/disable both Network Interface Cards (NICs).
- Power on the VM.
- After boot completes, power down the VM again.
- Reconnect/enable the lowest numbered NIC.
- Power on the VM.
The administrator should now be able to login to IDR console with idradmin initial credentials and complete the initial IDR configuration.
Related Articles
Unable to access the RSA Authentication Manager 8.1 Quick Setup page Number of Views Access Manger 6.1 aserver log shows 'Unable to send data to receiver' message Number of Views Unable to access RSA Authentication Manager Embedded Identity Router setup console Number of Views Which PKI credentials are stored on a RSA SecurID Smart Card 3100 and which standards does it follow? Number of Views Unable to check Database. java.lang.SecurityException: PBOX000016: Access denied: authentication failed Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?
