Email is not considered valid when setting up let's encrypt

elmar.fasel 2020-06-08 07:31:16 UTC #1

Keywords: SonarQube - Google Cloud Platform - Technical issue - Secure Connections (SSL/HTTPS)
bnsupport ID: d7e542f5-f8d2-b359-bb55-517812e2b5a9
Description:
support information: d7e542f5-f8d2-b359-bb55-517812e2b5a9
output when running "Set up Let's Encrypt" via the "Bitnami Helper Tool (0.1.0)"

Create a free HTTPS certificate with Let's Encrypt

Please provide a valid e-mail address for which to associate your Let's Encrypt
certificate.

Domain list: xxxxx

Server name: xxxxx

E-mail address: xxxxx

The Let's Encrypt Subscriber Agreement can be found at:

Do you agree to the Let's Encrypt Subscriber Agreement? [Y/n]: Y

Warning: Please enter a valid email

The email address I provide is our valid project email address, but not accepted here.
Any help is appreciated. Thanks.

Best regards,
Elmar

gongomgra 2020-06-08 10:05:04 UTC #2

Hi @elmar.fasel,

Can you tell us which email address are you using? Are you using an email address with format username@domain.com or similar?

The tool is internally verifying the value provided is not empty and it matches the next regular expression

^[a-z0-9.-_]+@[a-z0-9._-]+$

so it can contain lowercase letters,numbers,.,_,- both before and after the @ symbol

elmar.fasel 2020-06-08 10:30:22 UTC #3

Hi @gongomgra,

thanks for the regular expression. I think the problem is that it contains three ranges:

and not "lowercase letters,numbers,.,_,-" as you said.

What you probably want is 'a-z0-9._-'. If the '-' is at the end it does not define a range.

It's wrong before and after the '@'.

The email address I was trying to use is something like 'this-that@domain.com'

Best regards,
Elmar

gongomgra 2020-06-09 10:43:32 UTC #4

Hi @elmar.fasel,

You are right, the regular expression is defining a range instead of allowing -. I notified our Engineering Team for them to fix this issue and release a new bncert version with the fix. However, I can't give you an ETA of this.

You can create and configure your certificate manually using the next guide

https://docs.bitnami.com/aws/how-to/generate-install-lets-encrypt-ssl/#alternative-approach

elmar.fasel 2020-06-09 19:41:20 UTC #5

Hi @gongomgra,

thank you very much for the feedback. Glad I could help.

As a workaround I used a different email address, for now.
How would I replace this with the email address I wanted to use in the first place after the validation has been fixed? Can I then just rerun "Set up Let's Encrypt" via the "Bitnami Helper Tool"?

Best regards,
Elmar

gongomgra 2020-06-10 08:59:13 UTC #6

Hi @elmar.fasel,

Thanks for the info. I'm glad you managed to workaround this using a different email address. I think you can generate a new certificate using the bncert tool with the new email. We will let you know when is the new bncert released so you can update it.

Regards,
Gonzalo

system 2020-06-24 08:59:16 UTC #7

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

gongomgra 2020-06-26 07:11:11 UTC #8

gongomgra 2020-06-26 07:17:22 UTC #9

Hi @elmar.fasel,

Just a quick note to let you know that we released a new version of our bncert tool fixing this issue. Can you run it on your server again? It should detect there is a new version and it will ask you to update it. Please reply yes. Then, follow the next guide to revoke your current certificate

https://docs.bitnami.com/google/how-to/understand-bncert/#manually-revoking-an-existing-certificate

After that, you should be able to generate a new certificate using the other-user@domain.com email address.

Hope it helps,
Gonzalo

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!