By: Nikolaos Gkogktzilas user 28 May 2019 at 8:04 a.m. CDT

2 Responses
Nikolaos Gkogktzilas gravatar
Hi all, I am trying to have a local instance of gluu to develop some things on top of that. To do that i am following the k8s/minikube example. After reaching the end of the example tutorial i try to access the UI through `https://kube.gluu.local` but i get an error page saying `Oops. Something wrong happened. Return to the application using the button below.`. So having this issue i checked the logs in the container in `/opt/gluu/jetty/identity/logs/oxtrust.log` and i see this exception : ``` ERROR [qtp859417998-12] [org.xdi.oxauth.client.OpenIdConfigurationClient] (OpenIdConfigurationClient.java:175) - sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) ~[?:1.8.0_212] at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1946) ~[?:1.8.0_212] at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:316) ~[?:1.8.0_212] at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:310) ~[?:1.8.0_212] at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1639) ~[?:1.8.0_212] at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223) ~[?:1.8.0_212] . etc . etc . etc ``` So apparently i messed up some certificate. I am not really sure how to proceed fixing this. Does any of you maybe have some tips? Thnx in advance :D

By William Lowe staff 28 May 2019 at 8:16 a.m. CDT

William Lowe gravatar
We don't provide community support for K8. I would advise sticking to the regular VM-based container deployment strategy for testing.

By Mohan Manchikanti user 30 May 2019 at 4 a.m. CDT

Mohan Manchikanti gravatar
Hello Nikolaos Gkogktzilas, do you still have this issue, we had similar issue, just make sure to wait for `Config-init` pod to go to Completed status before progressing with further setup. Hope this helps :-)