HI. I know that is not a new problem, but with some other topic can't help me. Tried to obtain a cerificate with sudo certbot certonly --standalone or test sudo certbot certonly --dry-run The error is always the same. The server was stopped (FileMaker on Centos 7) The ports seem to be free: …

Welcome to the Let's Encrypt Community :slightly_smiling_face: Standalone spins up its own webserver that tries to listen on port 80. If port 80 is already bound, certbot will fail. Try using --webroot -w /path/to/your/website instead.

Problem binding to port 80: Could not bind to IPv4 or IPv6

Help

system Closed December 18, 2020, 6:35pm 5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Problem binding to port 80 with --standalone Help	6	240971	February 21, 2018
Problem binding to port 80: Could not bind to IPv4 or IPv6 Help	5	74495	May 26, 2018
Certbot unable to bind to port 80 in IPv4 Help	6	7990	August 22, 2019
Problem binding to port 80: Could not bind to IPv4 or IPv6 Help	4	2627	February 14, 2020
Certbot standalone server failed to bind to port using IPv4 Server	3	2832	August 14, 2017

Problem binding to port 80: Could not bind to IPv4 or IPv6

Related topics