My Oracle Support Banner

EM13c: '' Command Fails with SSLKeyException: Hostname Verification (Doc ID 2684786.1)

Last updated on MARCH 13, 2023

Applies to:

Enterprise Manager Base Platform - Version to [Release 13c]
Information in this document applies to any platform.


Excuted the script below to create the WebLogic encrypted configuration and key files.

<MIDDLEWARE_HOME>/OMSPatcher/wlskeys/ -oh <MIDDLEWARE_HOME> -location <location to put the encrypted files>

The oraclehome passed is valid.
Please enter weblogic admin server username: weblogic
Please enter weblogic admin server password:
Trying to get configuration and key files for the given inputs...
This operation will take some time. Please wait for updates...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 19, in connect
File "<iostream>", line 553, in raiseWLSTException
WLSTException: Error occurred while performing connect : Cannot connect via SSL. To connect via SSL, use the following two System properties as shown, java weblogic.WLST : Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3s://<OMS_VIRTUAL_HOSTNAME>:<WLS_ADMIN_PORT>: Destination <IP_ADDRESS>, <WLS_ADMIN_PORT> unreachable.; nested exception is: Hostname verification failed:, hostname=<OMS_VIRTUAL_HOSTNAME>.; No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.
Use dumpStack() to view the full stacktrace


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.