No, that's not it. How would that be the exact old valid certificate with the exact expiration of that expiring cert?
On Nov 22, 2016 8:52 AM, "Clayton Coleman" <[email protected]> wrote: > The router has a default certificate applied if no other certificate is > accepted - you may want to check that value for expiration (if your route > is misconfigured for another reason or has no endpoints). > > On Nov 22, 2016, at 2:31 AM, Dean Peterson <[email protected]> > wrote: > > Is the built in HA Proxy caching the information? How do I clear the > HAProxy cache in Openshift? > > On Tue, Nov 22, 2016 at 1:10 AM, Dean Peterson <[email protected]> > wrote: > >> How is this happening? I even removed the route entirely; it still shows >> the same certificate information even when showing a 503 error after the >> route is removed. The TLS information is only on the route. Is the router >> or Openshift caching the information somewhere? I have restarted Docker and >> the Openshift master and Node. >> >> On Mon, Nov 21, 2016 at 11:05 AM, Dean Peterson <[email protected]> >> wrote: >> >>> Hello, >>> >>> I have a route with TLS enabled. The RSA key, certificate and CA bundle >>> are all encoded in the route. I have an expiring TLS certificate. I renewed >>> and replaced the values of the certificate and CA bundle, removed and >>> updated the route. Unfortunately, the browser still shows the same >>> expiration date for the certificate. Does openshift cache TLS information; >>> do I need to do something other than deleting the route and recreating it >>> with the new values? >>> >> >> > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
