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 after executing: *rhc port-forward
keycloak.* (which
I could). I have not had a follow-up support since I confirmed this.
https://access.redhat.com/support/cases/#/case/01479959
On Thu, Jul 23, 2015 at 6:59 AM, Stian Thorgersen <stian(a)redhat.com> wrote:
Just got the same issue on my instance. Seems that after the instance
is
idled it returns this 502 even after the instance is restarted (confirmed
in the log that it's up and running).
----- Original Message -----
> From: "Ioan Eugen Stan" <stan.ieugen(a)gmail.com>
> To: "Stian Thorgersen" <stian(a)redhat.com>
> Cc: "keycloak-user" <keycloak-user(a)lists.jboss.org>
> Sent: Thursday, 23 July, 2015 12:45:56 PM
> Subject: Re: [keycloak-user] Keycloak OpenShift Cartridge updated to
1.3.1.Final
>
> Thank you for the response. However, I think it's another beast
altogether:
>
>
>
https://keycloak-ieugen.rhcloud.com/auth/admin/
>
> Proxy Error
>
> The proxy server received an invalid response from an upstream server.
> The proxy server could not handle the request GET /auth/admin/.
>
> Reason: DNS lookup failure for: 127.0.0.1:80auth
>
>
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
--
Michael J. Hills
Sr. CRM Architect
Mobile: 603.475.5093
Email : mike.hills(a)sematree.com
Skype : mhills_sematree