Oh right. Now that you mention it. I think I have encountered that before
too. I don’t remember the circumstances though.
On Mon, 8 Oct 2018 at 7:44 pm, Tim Dudgeon wrote:
> Yes, I had tried re-creating the route and that didn't work.
>
> Eventually I did manage to solve it. The 'Destination CA
Yes, I had tried re-creating the route and that didn't work.
Eventually I did manage to solve it. The 'Destination CA Cert' property
for the route was (automatically) filled with some place holder
'backwards compatibility' text. When I replaced this with the CA cert
used by the service (found
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 wrote:
> We've hit a problem with a HTTPS route that used to work fine has now
>
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
