This post helps those who are stuck with “Application is not available” on the OpenShift Console on IBM Virtual Private Cloud (VPC).
First, when you access the OpenShift Console you’ll see https://console-openshift-console.hidden.eu-gb.containers.appdomain.cloud/dashboards

Steps
- Find your worker nodes
$ oc get nodes -l node-role.kubernetes.io/worker
NAME STATUS ROLES AGE VERSION
worker0 Ready master,worker 28h v1.23.5+3afdacb
worker1 Ready master,worker 28h v1.23.5+3afdacb
2. Launch a debug pod to the node/worker0 and execute a chroot, and curl to confirm it times out.
$ oc debug node/worker0
Starting pod/1024204-debug ...
To use host binaries, run `chroot /host`
Pod IP: 10.242.0.4
If you don't see a command prompt, try pressing enter.
sh-4.4# chroot /host
curl google.com -v -k
* About to connect() to google.com port 80 (#0)
* Trying 216.58.212.238...
If the curl command never completes, then you probably don’t have the VPC set for egress.
3. Navigate to https://cloud.ibm.com/vpc-ext/network/subnet/
4. Find your subnet, click on Public Gateway

5. Retry accessing your Console (You can also retry from the command line oc debug). You should now see the dashboard (note it may need to retry the CrashBackOffLoop for the pod, so it may be a few minutes).

Appendix: Checking your Console URL
If you don’t know your external console URL, you can retrieve it from oc.
$ oc -n openshift-config-managed get cm console-public -o jsonpath='{.data.consoleURL}'
https://console-openshift-console.hidden.eu-gb.containers.appdomain.cloud
Appendix: Checking Access Tokens
If you are using OauthAccessTokens in your environment, and you closed your display, you can always get a view (as a kubeadmin) of the current access tokens using the OpenShift command line.
$ oc get oauthaccesstokens -A
NAME USER NAME CLIENT NAME CREATED EXPIRES REDIRECT URI SCOPES
sha256~-m IAM#yyy@ibm.com openshift-browser-client 12m 2022-06-22 15:00:38 +0000 UTC https://hiddene.eu-gb.containers.cloud.ibm.com:31871/oauth/token/display user:full
sha256~x IAM#g@ibm.com openshift-browser-client 10m 2022-06-22 15:02:24 +0000 UTC https://hiddene.eu-gb.containers.cloud.ibm.com:31871/oauth/token/display user:full
sha256~z IAM#x@us.ibm.com openshift-browser-client 171m 2022-06-22 12:21:30 +0000 UTC https://hiddene.eu-gb.containers.cloud.ibm.com:31871/oauth/token/display user:full
sha256~z IAM#y@ibm.com openshift-browser-client 131m 2022-06-22 13:01:18 +0000 UTC https://hiddene.eu-gb.containers.cloud.ibm.com:31871/oauth/token/display user:full
sha256~y IAM#y@ibm.com openshift-browser-client 84m 2022-06-22 13:48:29 +0000 UTC https://hiddene.eu-gb.containers.cloud.ibm.com:31871/oauth/token/display user:full
sha256~x IAM#y@ibm.com openshift-browser-client 130m 2022-06-22 13:02:25 +0000 UTC https://hiddene.eu-gb.containers.cloud.ibm.com:31871/oauth/token/display user:full
Appendix: Checking the OAuth Well Known
To check the well known oauth endpoints, check https://hidden-e.eu-gb.containers.cloud.ibm.com:30603/.well-known/oauth-authorization-server