break during Let's Encrypt SSL request
Installation script breaks on certificate request on the new clean Zbuntu server. A / AAA record works correctly. 2 weeks ago, the installation script also worked without problems.
Can anyone help me further?
> Using the webroot path /var/www/bigbluebutton-default for all unmatched domains.
> Waiting for verification...
> Challenge failed for domain bbb.mofi.de
> http-01 challenge for bbb.mofi.de
> Cleaning up challenges
> Some challenges have failed.
>
> IMPORTANT NOTES:
> - The following errors were reported by the server:
>
> Domain: bbb.mofi.de
> Type: unauthorized
> Detail: 138.201.221.210: Invalid response from
> http://bbb.mofi.de/.well-known/acme-challenge/17jjoY0hB7fwxhLxJrfomXAMI7na4JKCe-QR85hj5D8:
> 404
>
> To fix these errors, please make sure that your domain name was
> entered correctly and the DNS A/AAAA record(s) for that domain
> contain(s) the right IP address.
> - Your account credentials have been saved in your Certbot
> configuration directory at /etc/letsencrypt. You should make a
> secure backup of this folder now. This configuration directory will
> also contain certificates and private keys obtained by Certbot so
> making regular backups of this folder is ideal.
> bbb-install: Let's Encrypt SSL request for bbb.mofi.de did not succeed - exiting
>
I can confirm the same problem on my fresh Ubuntu 20.04. LTS
I also had no problems like this with my last BBB 2.5 installation on the same server (some months ago).
Are you installing 2.5 or 2.6-rc.4? If 2.6, can you try an install of 2.6 using bbb-install-2.6.sh and let me know that also fails.
I am trying to (re)install BBB 2.5.
I will give 2.5 one more try - hoping that it was just some issue with let's encrypt and if that fails again, I will try installing 2.6.
In either case I will give feedback here.
Are you installing 2.5 or 2.6-rc.4? If 2.6, can you try an install of 2.6 using
bbb-install-2.6.shand let me know that also fails.
with version 2.6-rc.4 it works fine. I think there must be an error in the 'bbb-install-2.5.sh' script.
Tested 2.5 yesterday with no problems on a bare-metal-server (Hetzner) with freshly installed and updated Ubuntu 20.04 LTS (no HWE). Domain has only an A-Record, no AAAA-Record. Will test it again today.
OT: Hi Mofi, man liest und trifft sich ja echt überall. 👋
Tested 2.5 yesterday with no problems on a bare-metal-server (Hetzner) with freshly installed and updated Ubuntu 20.04 LTS (no HWE). Domain has only an A-Record, no AAAA-Record. Will test it again today.
Good to know, since I am using a bare metal server from Hetzner, too. So I may try no HWE, if it keeps failing with HWE.
Fyi: The latest try to install 2.5 on Ubuntu 20.04. LTS (HWE) failed, too.
So I'm now going over to try other solutions. I will keep you informed.
I just have quickly gone through the terminal output. I'm getting some errors regarding apparmor missing. At the moment I can't tell for sure if this is the cause of the failing certbot challenge, too. I will give it a try and then report here.
Good news. The problem is really the missing dependency of apparmor.
Just install apparmor before starting bbb-install-2.5.sh and it works fine.
apt-get install apparmor
@muellerlukas: Does your Ubuntu 20.04. LTS (no HWE) come with apparmor preinstalled?
@Franz-Heinz Sorry, no. The term "freshly installed" was a little misleading. As of #600 I installed it first before using the script.
I have the same issue, unauthorized and Invalid response from. Did anyone solve it?
This is the bug of bbb-install for a long time and I don't know why BBB team doesn't fix it!!
To solve the issue, you can execute ufw disable first to turn off firewall, then use bbb-install again.
Have a good time.
This is the bug of
bbb-installfor a long time and I don't know why BBB team doesn't fix it!! To solve the issue, you can executeufw disablefirst to turn off firewall, then usebbb-installagain.Have a good time.
Thank you. I did something similar: ufw allow 80 and ufw allow 443
using version 2.7, i resolved the issue by configuring both IPv4 and IPv6 addresses for my ec2 instance and establishing corresponding A and AAAA dns records
Hi All,
I have the same problem on version 3.X (version 2.7 didn't work due to dependencies issue).
I tried ufw disable but didn't help. I also make sure that my hostname is the same as Im using in instalation command.
My server version: Ubuntu 22.04.3 LTS jammy
Any suggestion how solve this problem ? Please treat me as a noob and do not use thought shortcuts.
Hi All, I have the same problem on version 3.X (version 2.7 didn't work due to dependencies issue). I tried
ufw disablebut didn't help. I also make sure that my hostname is the same as Im using in instalation command. My server version: Ubuntu 22.04.3 LTS jammyAny suggestion how solve this problem ? Please treat me as a noob and do not use thought shortcuts.
OK I solved this problem. Im using cloudflare tunnel to reach my server. When I created appropriate public hostname, new DNS rekord has been created. After that problem with "Let's Encrypt" gone.
Thanks for sharing your update @smartkwadrat
Hi All, I have the same problem on version 3.X (version 2.7 didn't work due to dependencies issue). I tried
ufw disablebut didn't help. I also make sure that my hostname is the same as Im using in instalation command. My server version: Ubuntu 22.04.3 LTS jammyAny suggestion how solve this problem ? Please treat me as a noob and do not use thought shortcuts.
OK I solved this problem. Im using cloudflare tunnel to reach my server. When I created appropriate public hostname, new DNS rekord has been created. After that problem with "Let's Encrypt" gone.
What do u mean by "appropriate public hostname"?
It would be a fully qualified domain name that using DNS resolves to a public IP address of the server.
In other words, if you ping the hostname, it should return the public IP address after the DNS lookup.
