On Fri, Feb 28, 2025 at 10:25 AM Bo Berglund <bo.bergl...@gmail.com> wrote:
> On Fri, 28 Feb 2025 10:07:48 -0500, Frank Gingras <thu...@apache.org> > wrote: > > >On Fri, Feb 28, 2025 at 5:28?AM Bo Berglund <bo.bergl...@gmail.com> > wrote: > > > >> 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? > >> > >> > >That question may be better suited for the certbot / letsencrypt folks at > >this point. > > Well, their letsencrypt mail-list seems to have stopped back in 2018... > and there is no certbot list I have found on gmane... > > > -- > Bo Berglund > Developer in Sweden > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > > Moving to a modern mod_md approach might be better then, or alternatively, if you want to keep using the third party letsencrypt tools, asking your distro's support venues might work.
