On Fri, Feb 28, 2025 at 5:28 AM Bo Berglund <bo.bergl...@gmail.com> wrote:
> On Wed, 26 Feb 2025 11:30:12 -0500, Frank Gingras <thu...@apache.org> > wrote: > > > > > > >Nowadays, you should use mod_md: > > > >https://httpd.apache.org/docs/current/mod/mod_md.html > > Strange, one would assume that mod-md is a way to tell Apache to render > MarkDown > documents (filename.md), rather than handling renewal of letsencrypt > certs... > > > > Anyway, since I have moved/copied everything related to letsencrypt from > the old > to the new server, how can I disable letsencrypt renewals on the old > server and > enable on the new? > > If the old servers process starts it will be able to reach letsencrypt but > since > the router port forward no longer is set to the old server's letsencrypt > http > dir the check from letsencrypt will fail... > > So any handshake file placed there will not be seen by letsencrypt. > > OTOH the new server's handshake dir *is* available and therefore it should > be > the one handling renewals from now on. > > How can I shut down the renewal attempts from the old server and make sure > the > new server handles it? > > > -- > Bo Berglund > Developer in Sweden > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > > That question may be better suited for the certbot / letsencrypt folks at this point.
