Hi
Loving the Route10 product, just sharing random things I’ve found along the way.
Looks more of a tidy up or link to the let’s encrypt cert than anything else…
All the interfaces have an old expired self-signed cert running on them.
If you access any of the IP addresses (not the local.xxxxddns) you get a cert similar to the below
Wondering why this cert still exists, and isn’t being replace by the lets-encryt certs (understand will still get a warning however.
Good catch! That certificate is a placeholder for when we will eventually use the HTTPS server for some simple local admin operations using the Let’s Encrypt cert. The HTTP web server is enabled for initial setup, but we don’t use it for anything after that other than instructing clients that the device has already been set up on a controller.
I’m curious if this somehow played a role in a more recent issue I experienced with expired certs.
@Beaker Your expired certs were on the Control product, and they were Let’s Encrypt certs, so it would be a separate issue. If you are able to reproduce that, by the way, we’d definitely be interested in taking a look. From our analytics, though, we aren’t seeing a single Control device (software or appliance) with expired certs. Most likely there was something blocking the controller’s ability to renew the certificate.
