I have apache configured as a reverse SSL proxy.
Users connecting to the back end service are warned about the
certificate, which, when installed shows the cert has the domains of the
apache hosted site, not the proxy site. The apache hosted site/domains
names have their own valid certificates.
It's LetsEncrypt via acme-companion (dockerized) and checking the status
via the acme service shows the correct domain names. I suspect the
initial certificate was generated when I had some misconfiguration
Is apache caching the older cert or perhaps serving up it's own certificate?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Users connecting to the back end service are warned about the
certificate, which, when installed shows the cert has the domains of the
apache hosted site, not the proxy site. The apache hosted site/domains
names have their own valid certificates.
It's LetsEncrypt via acme-companion (dockerized) and checking the status
via the acme service shows the correct domain names. I suspect the
initial certificate was generated when I had some misconfiguration
Is apache caching the older cert or perhaps serving up it's own certificate?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org