Does the keycloak cartridge hardwire ips when it is "installed" into
a gear? Are these scalable applications, as in, were they created
with rhc app create .... -s
What happens if you restart the gear
rhc app restart -a mykeycloakapp
if that doesn't fix it then try
rhc app force-stop -a mykeycloakapp
rhc app start -a mykeycloakapp
This could help narrow down the problem. Because it either of those
work it is something about return from idling that is not getting
properly set with the routing layer.
On 07/23/2015 04:15 AM, Mike Hills
It's good to know I am not alone :)
I consistently receive this error on both the 1.2 and 1.3
versions of Keycloak running on OPENSHIFT ONLINE.
OPENSHIFT support had me validate that I could access my
keycloak instance at http://localhost:8080/auth
executing: rhc port-forward
keycloak. (which I could). I have not had a follow-up
support since I confirmed this.
keycloak-user mailing list