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

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:
micca.hopto.org

I ran this command:
certbot certonly --standalone --preferred-challenges http -d micca.hopto.org

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for micca.hopto.org
Cleaning up challenges
Problem binding to port 80: Could not bind to IPv4 or IPv6.

My web server is (include version): pleroma following this howto:
https://docs-develop.pleroma.social/backend/installation/otp_en/

The operating system my web server runs on is (include version):
Ubuntu 18.04.3 LTS x86_64

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know): yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): 0.27.0

1 Like

--standalone signals certbot to spin up a temporary web service to process the validation.
[which requires the full use of port 80]
If you already have a web server running you might opt to use that one instead.
If you don’t have one… then maybe certbot is running in --standalone mode twice?

1 Like

ss -tlnp | grep -E “:(80|443)”

LISTEN 0 128 0.0.0.0:80 0.0.0.0:* users:((“lighttpd”,pid=1948,fd=4))
LISTEN 0 128 [::]:80 [::]:* users:((“lighttpd”,pid=1948,fd=5))
LISTEN 0 50 *:8081 : users:((“qbittorrent”,pid=2401,fd=35))

I think that lighttpd might be from something else I tried. Know of a way to shut it down?

1 Like

nvm, I figured it out.

1 Like

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