Have you tried looking at the generated haproxy file inside the router? It might give some hints as to what went wrong. I presume you’ve already tried recreating the route? On Wed, 3 Oct 2018 at 2:30 am, Tim Dudgeon <tdudgeon...@gmail.com> wrote:
> We've hit a problem with a HTTPS route that used to work fine has now > stopped working. > Instead of the application we're are seeing the 'Application is not > available' page from the router. > > The route is using 'reencrypt' termination type to hit the service on > port 8443. > The service itself and its pod is running OK as indicated by being able > to curl it from inside the router pod using: > > curl -kL https://secure-sso.openrisknet-infra.svc:8443/auth > > (the -k is needed). > > An equivalent HTTP route that hits the HTTP service on port 8080 is > working fine. > > The only thing I can think of that might have caused this is redeploying > the master certificates using the 'redeploy-certificates.yml' playbook, > but I can't see how that would cause this. > This is all with Origin 3.7. > > Any thoughts on what might be wrong here? > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
