Accidentally Unsubscribed


#12

Sorry, this is a bug in Certbot. There’s a pending fix at https://github.com/certbot/certbot/pull/3165.

You may be able to apply that patch locally if you find your local copy of acme/acme/client.py.

Actually, looking again at where this error happens, it’s after Certbot has updated your email. So I think your update was successful even though Certbot errored out afterwards.


Error while updating email address
#13

Any updated on this yet?
Cheers!


#14

No updates yet, sorry!


#15

Exact same thing happend to me. :pensive: Clicked the link in a caffeine depleted state… Will certbot register --update-registration work? Changing email address is unfortunately not an option for me…

Ps. Mandrill should at least but a confirm button on that unsub page… :astonished:


#16

certbot register --update-registration will only update the email address, but if the address doesn’t change, you won’t be receiving any emails. Short of changing your address, there’s currently no way to fix this.


#17

Just hit it by accident too.

Am I right in assuming I won’t receive updates for any sites that use the email in question?


#18

I have accidentally unsubscribed as well. I am posting here so that I can send a PM to get it reversed.


#19

Update: Unfortunately we can’t do one-off removals by private message anymore. There are instructions on https://letsencrypt.org/docs/expiration-emails/ about how to work around an accidental unsubscribe.


#20

The command should work ?

Why there are no confirm unsubscribe buton.
At least can you minimize your link in mail, the link took 80% on email size I think there are many people who click on accidentally…


#21

Unfortunately this is implemented on the side of our email provider and we don’t have the ability to make changes. I agree that it would be a lot better if we they confirmed the intent before unsubscribing!

I recently added some additional text to the email to make it clearer that it won’t confirm the unsubscribe action. This should be rolled out to the production emails in the next while. Hopefully that helps somewhat!

Thanks.


#22

Ok but the command provided with cerbot should work ?


#23

Yes. ~/certbot/venv/bin/certbot register --update-registration --email yourname+1@example.com should work. You might have to change the ~/certbot/venv/bin portion based on where/how you installed Certbot.


#24

Hi guys I accidentally unsubscribed. I meant to click on different window which was in front of this email, Anyone please post how you manage to get expiry notifications working again with satisfaction. Thanks


#25

I unsubscribed because I didn’t want any more notifications those domains mentioned in the email.
I realize that I unsubscribed from notifications from all my domains.

Maybe you should clarify that in the text next to the link, that the link unsubscribes from notification from all domains, not only those in the current email.


#26

I created https://github.com/letsencrypt/boulder/issues/2719 for this suggestion. Thanks


#27

I’ve just had this issue - hopefully this doesn’t affect all the domains that we’ve signed up to?

We are using a company-wide email, and this may affect more than just one domain.

Is there not any way you could add a re-subscribe feature?


#28

If you unsubscribe from one expiration warning email it will unsubscribe that address from all future expiration warnings.

Presently this isn’t possible. It’s a non-trivial amount of work and the expiration warnings are a best effort service. I recommend that for large organizations in particular that you have monitoring in place above and beyond the expiration warnings for the certificates you rely on.

Apologies for the poor experience. Can you use the workaround described on the expiration email docs page?

However, you can change the email address on your account, which effectively re-subscribes you. Many common email services treat yourname+1@example.com the same as yourname@example.com. So if you update your email address to yourname+1@example.com, you can start getting expiry mail again. With Certbot, use:

certbot register --update-registration --email yourname+1@example.com


#29

Okay, well thank you for answering my question.

Only thing I would ask, would you be able to add a pre-unsubscribe notice; e.g. “Are you sure you wish to unsubscribe?”

I can’t help but think that this thread wouldn’t exist if that pre-check had been applied already?

IMHO / In My Humble Opinion.


#30

Unfortunately we can’t since the service we use for sending email is responsible for generating the link ID and manages the unsubscribes. They have implemented it as a one-click action.


#31

One example that was created by a community member here (and is not affiliated with Let’s Encrypt) is

https://letsmonitor.org/

It uses a slightly different approach than the Let’s Encrypt expiration notices. The latter are based on a history of all certificates ever issued by Let’s Encrypt, while the former are based on actively monitoring whatever is being used by a particular specified site. So for example if you issued a Let’s Encrypt cert for example.com and example.net, and then you completely stopped using example.net and renewed the cert only for example.com,

  • the Let’s Encrypt warnings would say that you had failed to renew your example.net cert, because the CA knows that you once had a particular cert configuration and you no longer do, while

  • the Let’s Monitor warning would say that everything was fine, if you had only signed up to monitor example.com, because at least that site still has a valid cert.