Re: py39-certbot-2.6.0,1

On 11/16/23 2:02 PM, Doug Hardie wrote:
>> On Nov 16, 2023, at 13:59, TIM KELLERS <trkellers@gmail.com> wrote:
>>
>> 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.
>>
>>
>> Tim
>>
>>
>> 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:
>>>
>>> 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.
>>>
>>> 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,
>>>
> 
> 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.
> 

have you added any vhosts or 301 redirects on port 80 in your httpd 
configuration?  i have this issue with one system that does a 301 
redirect to port 443 on port 80.  on another host where i don't do this 
certbot works as expected without having to stop httpd.

-pete


-- 
Pete Wright
pete@nomadlogic.org