./letsencrypt-auto command not found

Help
1

I ran this command:
sudo ./letsencrypt-auto --apache -d <my_domain>

It produced this output:
sudo: ./letsencrypt-auto: command not found

My web server is (include version):
Apache/2.4.52 (Ubuntu)

The operating system my web server runs on is (include version):
Ubuntu Server (actually, this is a VM inside my main Manjaro system, but it's working fine so far)

My hosting provider, if applicable, is:
dynu.com (this is my DDNS provider, if I understand well the request)

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):
I don't know... how can I verify?

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

Please, help! Thank you so much!

2

Hi @vicentemmos, and welcome to the LE community forum :slight_smile:

Try:
certbot --apache -d <my_domain>

How do you manage the system?
How do you make changes to it?

That version is a bit outdated.
Check for a possible newer/better version: Certbot Instructions | Certbot (eff.org)

Since we are dealing with Apache, I like to start by looking at the output of:
sudo apachectl -t -D DUMP_VHOSTS

3 Likes
3

Hi! Thank you! =)

I tried updating certbot, as per your suggestion, following this guide:

Then, I tried running both

sudo certbot --apache

and

sudo certbot certonly --apache

but I get similar errors. Since I'm running Ubuntu Server, on a VM no less, I can't copy/paste the entire output here, so I'll at lease write a few lines:

AH0058: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
(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

I suppose this error message is telling me that TCP port 80 in my router is already in use. I tried adding port forwarding rules, and managed to connect my router to my DDNS, but there's something I'm still missing...

By the way:

$ sudo apachectl -t -D DUMP_VHOSTS
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
VirtualHost configuration:
*:80                         127.0.1.1  (/etc/apache2/sites-enabled/000-default.conf:1)
4

Looks like you don't using apache? If its already running certbot wont try to start it
Whats the domain name?

3 Likes
5

I honestly have little to no idea about what I'm doing. I have apache in my machine, I also installed certbot. So I should be using either or? The domain name is vmmos-nextcloud.freeddns.org. But what do I need to do?

6

disable https redirect currenty: you are not replying over https so challange can't complete

2 Likes
7

what guide thing you were looking at while setting certbot/apache etc?

2 Likes
8

disable https redirect currenty: you are not replying over https so challange can't complete

Honestly, I don't understand what you just told me here... I have no idea what you meant.

what guide thing you were looking at while setting certbot/apache etc?

I sent the link in my response to rg305... it's this one:

a link from certbot's page itself.

9

no, before that, installing ubuntu, install apache etc

3 Likes
10

Sadly, it shows:

Let's have a look at this file:

3 Likes
11

Hey, everyone! Good morning.

Sorry it took me a bit long to reply... I was trying so many different things, left and right, it would be impractical to keep writing here. Anyway, I wanted to let everyone here know I managed to fix the problem. My server is working with a new DDNS, thanks to ChatGPT no less, which gave me so many instructions and follow up.

I still have to do some improvements to it, but those are definitely not as difficult to implement. Geez, who'd have thought leaving Google would be this much work! Either way, thanks everyone, this ticket can be now closed.

1 Like
12

You know you're not supposed to use the console on your cloud provider's website, right?

2 Likes
13

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