Certificate not valid on www.paysy.in but valid for paysy.in

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:paysy.in

I ran this command:

It produced this output:

My web server is (include version):nginx/1.18.0

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

My hosting provider, if applicable, is:aws

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):

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

Error when I access www.paysy.in
This server could not prove that it is www.paysy.in ; its security certificate is from paysy.in . This may be caused by a misconfiguration or an attacker intercepting your connection.

Can I have multiple host name on my certificate to resolve this error ? If yes then how can I do this for my existing certificate

But paysy.in works fine.

2

There is no active cert issued that covers the FQDN "www.paysy.in".
You should reissue the cert - with both names on it.

Yes.

Adjust your last certbot request to include both names (not just one name).

1 Like
3

How can i do this ?

4

How did you get he cert you have now?

1 Like
5

sudo certbot certonly --standalone -d paysy.in

And then I renewed once because it got expired.

6

Then try:
sudo certbot certonly --standalone -d paysy.in -d www.paysy.in

1 Like
7

I will try this and let you know if I face any issues. Thank you so much for the real time replies.

1 Like
8

sudo certbot certonly --standalone -d paysy.in -d www.paysy.in

After executing this I am getting this error :
An unexpected error occurred:
The client lacks sufficient authorization :: Account is not valid, has status "deactivated"

9

when i do this:
certbot register

I get this error:

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

There is an existing account; registration of a duplicate account with this command is currently unsupported.

10

Well, that is unexpected.

Try these:
certbot unregister
certbot register

[walk through the prompts]

Then (again):
sudo certbot certonly --standalone -d paysy.in -d www.paysy.in

1 Like
11

So I had done certbot unregister a while ago while renewing. By mistake I did that
And I raised a support ticket for that as well.
they had asked me to do certbot register but that didnt seem to be working for me

12

After certbot register :
There is an existing account; registration of a duplicate account with this command is currently unsupported.

13

Please just follow my instructions.

1 Like
14

Sure, this is what happens when I do certbot unregister

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

Are you sure you would like to irrevocably deactivate your account?

(D)eactivate/(A)bort: D

An unexpected error occurred:

The client lacks sufficient authorization :: An account with the provided public key exists but is deactivated

Please see the logfiles in /var/log/letsencrypt for more details.

15

run as root
OR
use sudo

sudo certbot unregister
sudo certbot register

1 Like
16

Same error

sudo certbot unregister

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

Are you sure you would like to irrevocably deactivate your account?

(D)eactivate/(A)bort: D

An unexpected error occurred:

The client lacks sufficient authorization :: An account with the provided public key exists but is deactivated

Please see the logfiles in /var/log/letsencrypt for more details.

17

Well that is very unexpected.

Try:

1 Like
18

sudo certbot register

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

There is an existing account; registration of a duplicate account with this command is currently unsupported.

19

how do I do this

delete the account from inside the /etc/letsencrypt/accounts directory

20

Should I just directly delete /etc/letsencrypt/accounts directory ?