Bootstrap FreeKB - IBM WebSphere - Resolve "site can't be reached, unable to connect"
IBM WebSphere - Resolve "site can't be reached, unable to connect"

Updated:   |  IBM WebSphere articles

Let's say you get "This site can't be reached" or "unable to connect" when attempting to access the WebSphere admin console.

 


Determine if WebSphere is running

If you have access to the server running WebSphere, use the serverStatus command to determine if WebSphere is up and running.

~]# ${WAS_INSTALL_ROOT}/profiles/your_profile/bin/serverStatus.sh
ADMU0509I: The Deployment Manager "dmgr" is STARTED.

 


Check DNS

The nslookup command can be used to determine if DNS is able to resolve the hostname to the IP address of your server running WebSphere. If not, DNS will need to be configured.

C:\> nslookup www.example.com
Server:   ns1.example.com
Address:  10.80.140.51

Non-authoritative answer:
Name:    www.example.com
Address:  10.81.146.140

 


Check the logs

The WebSphere logs, such as the SystemOut.log or HPEL logs, may have events that can be used to troubleshoot the issue. Refer to Getting Started with logging on WebSphere.

 


TLS version

According to https://support.google.com/chrome/a/answer/7679408, starting with version 98 of Google Chrome, TLS versions 1.0 and 1.1 are no longer allowed. If WebSphere is configured to use TLS 1.0 or 1.1, this can cause "this site can't be reached" to be returned. In this scenario, refer to Configure SSL TLS authentication, protocol, providers, and ciphers (QoP) to update WebSphere to use TLS version 1.2 or higher.

 




Did you find this article helpful?

If so, consider buying me a coffee over at Buy Me A Coffee



Comments


Add a Comment


Please enter 921167 in the box below so that we can be sure you are a human.