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

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:

s -tlnp | grep -E ":(80|443)"
LISTEN 0 128 [::]:80 [::]:*
LISTEN 0 128 [::]:443 [::]:*

What can I do ?

1 Like

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.


Thanks, now the certificate is generated and installed (i've used also some tips from the MacOS script installer).

But a new problem, accesing remotely the server seems that the certificate is not valid, accessing local seems it's good.

Now the certificate is valid also remotely, maybe i've just to wait some time. :smile:

1 Like

Happy it's working!


Usually a stale cache is to blame for not seeing the update.

1 Like

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