Next cloud swag certification error

Help
41

No. Now you should...

See: Rate Limits - Let's Encrypt

1 Like
42

Ok so I can continue to try

1 Like
43

Domain: www.misteratunas.duckdns.org

Type: unauthorized

Detail: Invalid response from http://www.misteratunas.duckdns.org/.well-known/acme-challenge/e8xohuICKs74o3ByGN3Gr3pqUPiZmcWMIJKN-YdwG_A [90.90.123.131]: "\n\n\t\n\t\topenmediavault - HTTP 404 error\n\t\t<meta charset="UTF-8">\n\t\t<meta http-equiv="X-U"

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Some challenges have failed.

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.

ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

44

I really do not know why

45

This message is confusing:

[MediaVault is already using port 80]

We should review this log file:

46

I see that in the ssh terminal ?

47

Yes.
cat /var/log/letsencrypt/letsencrypt.log

48

root@OpenMediaVault:~# /var/log/letsencrypt/letsencrypt.log
-bash: /var/log/letsencrypt/letsencrypt.log: No such file or directory

49

use cat

50

root@OpenMediaVault:~# cat /var/log/letsencrypt/letsencrypt.log
cat: /var/log/letsencrypt/letsencrypt.log: No such file or directory

51

Well that was unexpected :frowning:

Try searching the MediaVault site for clues on how they implement their ACME client and how one should troubleshoot their process.

52

It's not a good sign ?

53

Because I asked in my machine with root in local

54

Try these:
which certbot
certbot certificates

55

root@OpenMediaVault:~# certbot certificates
-bash: certbot: command not found

root@OpenMediaVault:~# which certbot
root@OpenMediaVault:~#

56

Try:
find / -name certbot

57

root@OpenMediaVault:~# find / -name certbot
/var/lib/docker/overlay2/0720cd5edcdb9870f45a913ed5e8c3a19291ea7f6c832846ef501470b8bcf1f2/merged/usr/lib/python3.9/site-packages/certbot
/var/lib/docker/overlay2/0720cd5edcdb9870f45a913ed5e8c3a19291ea7f6c832846ef501470b8bcf1f2/merged/usr/bin/certbot
/var/lib/docker/overlay2/0720cd5edcdb9870f45a913ed5e8c3a19291ea7f6c832846ef501470b8bcf1f2/diff/usr/lib/python3.9/site-packages/certbot
/var/lib/docker/overlay2/dd3b1273e1588ac5478dc08a9e7b2db4d303525bef3a9383c138fc879bf2b345/diff/usr/lib/python3.9/site-packages/certbot
/var/lib/docker/overlay2/dd3b1273e1588ac5478dc08a9e7b2db4d303525bef3a9383c138fc879bf2b345/diff/usr/bin/certbot
find: ‘/proc/9219/task/9219/net’: Invalid argument
find: ‘/proc/9219/net’: Invalid argument

58

show:
ls -l /etc/letsencrypt/*
ls -l /config/letsencyrpt/etc/letsencrypt/*

59

root@OpenMediaVault:~# ls -l /etc/letsencrypt/*
ls: cannot access '/etc/letsencrypt/*': No such file or directory

root@OpenMediaVault:~# ls -l /config/letsencyrpt/etc/letsencrypt/*
ls: cannot access '/config/letsencyrpt/etc/letsencrypt/*': No such file or directory

60

Ok I give up.