Certificate for local server

My domain is: jedsweb.com

I ran this command: sudo apt install snapd

sudo snap install core; sudo snap refresh core

sudo snap install --classic certbot

sudo ln -s /snap/bin/certbot /usr/bin/certbot

sudo certbot –apache

It produced this output: jeds@jedsweb:~$ sudo snap install core; sudo snap refresh core

snap "core" is already installed, see 'snap help refresh'

snap "core" has no updates available

jeds@jedsweb:~$ sudo snap install --classic certbot

snap "certbot" is already installed, see 'snap help refresh'

jeds@jedsweb:~$ sudo ln -s /snap/bin/certbot /usr/bin/certbot

ln: failed to create symbolic link '/usr/bin/certbot': File exists

jeds@jedsweb:~$ sudo certbot --apache

Saving debug log to /var/log/letsencrypt/letsencrypt.log

Enter email address or hit Enter to skip.

(Enter 'c' to cancel): fines.higher75@gmail.com


Please read the Terms of Service at:

You must agree in order to register with the ACME server. Do you agree?


(Y)es/(N)o: Y


Would you be willing, once your first certificate is successfully issued, to

share your email address with the Electronic Frontier Foundation, a founding

partner of the Let's Encrypt project and the non-profit organization that

develops Certbot? We'd like to send you email about our work encrypting the web,

EFF news, campaigns, and ways to support digital freedom.


(Y)es/(N)o: Y

Account registered.

Please enter the domain name(s) you would like on your certificate (comma and/or

space separated) (Enter 'c' to cancel): jedsweb.com

Requesting a certificate for jedsweb.com

Error while running apache2ctl graceful.

httpd not running, trying to start

(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80

(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80

no listening sockets available, shutting down

AH00015: Unable to open logs

Unable to restart apache using ['apache2ctl', 'graceful']

Error while running apache2ctl graceful.

httpd not running, trying to start

(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80

(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80

no listening sockets available, shutting down

AH00015: Unable to open logs

Unable to restart apache using ['apache2ctl', 'graceful']

Encountered exception during recovery: certbot.errors.MisconfigurationError: Error while running apache2ctl graceful.

httpd not running, trying to start

(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80

(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80

no listening sockets available, shutting down

AH00015: Unable to open logs

Error while running apache2ctl graceful.

httpd not running, trying to start

(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80

(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80

no listening sockets available, shutting down

AH00015: Unable to open logs

Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

jeds@jedsweb:~$

My web server is (include version): nextcloud (installed during ubuntu server install)

The operating system my web server runs on is (include version): ubuntu 24.04.3 server

My hosting provider, if applicable, is: server is on my local network

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): don’t know

My website is live and I can log into nextcloud. I can also ssh into the server from 3 clients using ssl generated passphrases. I just want to secure the domain with Https

certbot 5.2.2

Your server cannot be reached from the public internet using HTTP on port 80.

This isn't unique to Let's Encrypt. None of these locations can see your server: Check website performance and response : Check host - online website monitoring

You should check connections from outside your local network.

The "could not bind to address ..." message means Apache could not open that port (80) for its own use. Something else must have been using it. You'll need to sort out which service you want handling which port.

I don't know anything about Nextcloud. But, if you want Apache to use port 80 you need to make it available to it.

2 Likes