Date: Thu, 16 Nov 2023 14:02:39 -0800 From: Doug Hardie <bc979@lafn.org> To: TIM KELLERS <trkellers@gmail.com> Cc: questions@freebsd.org Subject: Re: py39-certbot-2.6.0,1 Message-ID: <8D21AE27-BE70-4158-B198-4B06C7D4A981@sermon-archive.info> In-Reply-To: <173e9c01-1e50-43ce-8acb-22a33f9603d4@gmail.com> References: <E9299A1C-27B1-46CE-95B3-926AAEA56DF1@sermon-archive.info> <173e9c01-1e50-43ce-8acb-22a33f9603d4@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_FFAB6EFA-115B-4B15-A65C-4A65A7E0C21D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
> On Nov 16, 2023, at 13:59, TIM KELLERS <trkellers@gmail.com> wrote:
>=20
> I use that certbot, too, and I just do an apachectl stop before =
"certbot renew." I also have to stop the pf service because my firewall =
doesn't like port 80 traffic, but that's a different use case.
>=20
>=20
>=20
> Tim
>=20
>=20
>=20
> On 11/16/23 4:34 PM, Doug Hardie wrote:
>> I have been using py39-certbot-2.6.0,1 for sometime now without any =
issues. However, earlier this month it started generating errors:
>>=20
>> Renewing an existing certificate for sermon-archive.info and 5 more =
domains
>> Failed to renew certificate sermon-archive.info with error: Could not =
bind TCP port 80 because it is already in use by another process on this =
system (such as a web server). Please stop the program in question and =
then try again.
>>=20
>> Huh? Of course there is a web server there. That's why I need a =
certificate. Anyone know how to fix this issue, or should I switch to =
some other LetsEncrypt client? Thanks,
>>=20
Stopping the web server is not a viable approach. It is on a production =
machine and that would affect my clients. It has never done this in the =
years I have been using LetsEncrypt. I don't see any changes in that =
port either.
-- Doug
--Apple-Mail=_FFAB6EFA-115B-4B15-A65C-4A65A7E0C21D
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
charset=us-ascii
<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><blockquote type="cite"><div>On Nov 16, 2023, at 13:59, TIM KELLERS <trkellers@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div><p>I use that certbot, too, and I just do an apachectl stop before
"certbot renew." I also have to stop the pf service because my
firewall doesn't like port 80 traffic, but that's a different use
case.</p><p><br>
</p><p>Tim<br>
</p>
<div class="moz-signature"><p><br>
</p>
<font size="2" face="sans-serif" color="gray">
<!-- a href="http://twitter.com/njitcpe"><img alt="CPE Twitter" style="padding:2px;" hspace="2" vspace="2" src="http://dl1.njit.edu/~bpenczak1/tw.png"></img></a>;
<a href="https://www.laverne.edu"><img alt="CPE Facebook" style="padding:2px;" hspace="2" vspace="2" src="http://dl1.njit.edu/~bpenczak1/fb.png"></img></a -->
</font></div>
<div class="moz-cite-prefix">On 11/16/23 4:34 PM, Doug Hardie wrote:<br>
</div>
<blockquote type="cite" cite="mid:E9299A1C-27B1-46CE-95B3-926AAEA56DF1@sermon-archive.info">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
I have been using py39-certbot-2.6.0,1 for sometime now without
any issues. However, earlier this month it started generating
errors:
<div><br>
</div>
<div>
<div>Renewing an existing certificate for sermon-archive.info
and 5 more domains</div>
<div>Failed to renew certificate sermon-archive.info with error:
Could not bind TCP port 80 because it is already in use by
another process on this system (such as a web server). Please
stop the program in question and then try again.</div>
<div><br>
</div>
<div>Huh? Of course there is a web server there. That's why I
need a certificate. Anyone know how to fix this issue, or
should I switch to some other LetsEncrypt client? Thanks,</div>
<div><br>
</div>
</div></blockquote></div></div></blockquote><br></div><div>Stopping the web server is not a viable approach. It is on a production machine and that would affect my clients. It has never done this in the years I have been using LetsEncrypt. I don't see any changes in that port either.</div><div><br></div><div>-- Doug</div><div><br></div><br></body></html>
--Apple-Mail=_FFAB6EFA-115B-4B15-A65C-4A65A7E0C21D--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8D21AE27-BE70-4158-B198-4B06C7D4A981>