# Not receiving email alerts anymore

**URL:** <https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843>\
**Category:** Help\
**Created:** [March 18, 2018, 10:54am UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843 "2018-03-18T10:54:37Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Carolyn](https://avatars.discourse-cdn.com/v4/letter/c/3ab097/32.png) [@Carolyn](https://community.letsencrypt.org/u/Carolyn)\
**Post date:** [March 18, 2018, 10:54am UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/1 "2018-03-18T10:54:37Z")

</div>

Good morning  
I am not receiving any emails anymore for when my certificates are going to expire.  
I can not find where to re-enter this. can anybody help me ?

thanks in advance.  
Carolyn

---

<div class="post-metadata">

**Author:** ![jmorahan](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jmorahan/32/1873_2.png) [@jmorahan](https://community.letsencrypt.org/u/jmorahan)\
**Post date:** [March 18, 2018, 11:51am UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/2 "2018-03-18T11:51:52Z")

</div>

Did you accidentally click an unsubscribe link? The link unsubscribes you from _all_ expiry notifications, not just a particular certificate or domain.

I don't believe there's currently any way to re-subscribe with the same email address, but you can change the email address on your account and it will subscribe the new one. As [Expiration Emails - Let's Encrypt](https://letsencrypt.org/docs/expiration-emails/) says:

> However, you can change the email address on your account, which effectively re-subscribes you. Many common email services treat [yourname+1@example.com](mailto:yourname+1@example.com) the same as [yourname@example.com](mailto:yourname@example.com). So if you update your email address to [yourname+1@example.com](mailto:yourname+1@example.com), you can start getting expiry mail again. With Certbot, use:
> 
> `~/certbot/venv/bin/certbot register --update-registration --email yourname+1@example.com`

(or instead of `~/certbot/venv/bin/certbot` just use `certbot` or `certbot-auto` or whatever, depending on how you installed it)

---

<div class="post-metadata">

**Author:** ![Carolyn](https://avatars.discourse-cdn.com/v4/letter/c/3ab097/32.png) [@Carolyn](https://community.letsencrypt.org/u/Carolyn)\
**Post date:** [March 18, 2018, 12:16pm UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/3 "2018-03-18T12:16:07Z")

</div>

Hi  
Thanks for your speedy reply.  
I don’t think i did, but i’m guessing that it must probably be the case.

I’ve seen the instruction you sent on how to change the email address using certbot, but i don’t think i’m using certbot.  
To be honest, i’m not a developper (and i’m blonde to boot!)  
I did the following to install letsencrypt :

To install letsencrypt utility i typed : sudo apt-get install -y letsencrypt

Then to lauch lets Encrypt certification I typed : sudo letsencrypt certonly -d [domainename.com](http://domainename.com)  
And entered the e-mail address

Each time i renew, i just type :  
_sudo letsencrypt certonly -d [domainename.com](http://domainename.com)_

So I’m not sure what i should now type to re-enter an email address.  
Should i retype : _sudo letsencrypt --update-registration [--myemain@domain.com](mailto:--myemain@domain.com)_

Thanks in advance for your help and patience.  
Carolyn

---

<div class="post-metadata">

**Author:** ![jmorahan](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jmorahan/32/1873_2.png) [@jmorahan](https://community.letsencrypt.org/u/jmorahan)\
**Post date:** [March 18, 2018, 12:22pm UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/4 "2018-03-18T12:22:42Z")

</div>

> [@Carolyn](#):
>
> Should i retype : sudo letsencrypt --update-registration [--myemain@domain.com](mailto:--myemain@domain.com)

`letsencrypt` and `certbot` are the same thing, it just got renamed a while ago. The command you posted _should_ work, but note that the `--update-registration` option was added in version 0.8.0 so if you have an older version it won't work and you might need to upgrade it. You can find what version you're using by typing `letsencrypt --version`

If you need help upgrading letsencrypt/certbot, let us know what operating system you're using.

---

<div class="post-metadata">

**Author:** ![jmorahan](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jmorahan/32/1873_2.png) [@jmorahan](https://community.letsencrypt.org/u/jmorahan)\
**Post date:** [March 18, 2018, 12:24pm UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/5 "2018-03-18T12:24:34Z")

</div>

> [@Carolyn](#):
>
> sudo letsencrypt --update-registration [--myemain@domain.com](mailto:--myemain@domain.com)

Sorry, just noticed a couple of errors in this, it should actually be

```
sudo letsencrypt register --update-registration --email myemain@domain.com

```

---

<div class="post-metadata">

**Author:** ![Carolyn](https://avatars.discourse-cdn.com/v4/letter/c/3ab097/32.png) [@Carolyn](https://community.letsencrypt.org/u/Carolyn)\
**Post date:** [March 18, 2018, 12:43pm UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/6 "2018-03-18T12:43:07Z")

</div>

ok… i checked the version of letsencrypt on one of my servers (there are 5 in all) is 0.4.1  
So i guess i need to update my letsencrypt.

I connect to my distant server (on which I’ve installed letsencrypt) using PuTTY since i have a windows pc.

The distant servers are OVH vps

Carolyn

---

<div class="post-metadata">

**Author:** ![Carolyn](https://avatars.discourse-cdn.com/v4/letter/c/3ab097/32.png) [@Carolyn](https://community.letsencrypt.org/u/Carolyn)\
**Post date:** [March 18, 2018, 12:46pm UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/7 "2018-03-18T12:46:33Z")

</div>

> [@jmorahan](#):
>
> > [@Carolyn](#):
> >
> > sudo letsencrypt --update-registration [--myemain@domain.com](mailto:--myemain@domain.com)
> 
> Sorry, just noticed a couple of errors in this, it should actually be
> 
> ```
> sudo letsencrypt register --update-registration --email myemain@domain.com
> 
> ```

> [@jmorahan](#):
>
> sudo letsencrypt register --update-registration --email [myemain@domain.com](mailto:myemain@domain.com)

I tried this, just in case we'd have any luck, but i got the following error message :

_unrecognized arguments: register --update-registration_

---

<div class="post-metadata">

**Author:** ![jmorahan](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jmorahan/32/1873_2.png) [@jmorahan](https://community.letsencrypt.org/u/jmorahan)\
**Post date:** [March 18, 2018, 12:51pm UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/8 "2018-03-18T12:51:14Z")

</div>

> [@Carolyn](#):
>
> I tried this, just in case we’d have any luck, but i got the following error message :
> 
> unrecognized arguments: register --update-registration

Right, you'll need to upgrade first.

Do you know what operating system is running on the VPS? Ubuntu, Debian, CentOS, something else? Ubuntu 16.04 packages letsencrypt 0.4.1 so that might be what you've got?

Also, what web server are you using? Apache, nginx, etc?

The instructions for installing and using the latest version of certbot are at [https://certbot.eff.org/](https://certbot.eff.org/) but you need to know the operating system and web server.

---

<div class="post-metadata">

**Author:** ![Carolyn](https://avatars.discourse-cdn.com/v4/letter/c/3ab097/32.png) [@Carolyn](https://community.letsencrypt.org/u/Carolyn)\
**Post date:** [March 18, 2018, 1:13pm UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/9 "2018-03-18T13:13:10Z")

</div>

It’s Linux Ubuntu 16.04 but I can’t find on the OVH site what web server is used (and you don’t get the choice when configuring the server) so I’ll check with OVH tomorrow for the web server.  
thanks so much for your help today 🙂

Carolyn

---

<div class="post-metadata">

**Author:** ![jmorahan](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jmorahan/32/1873_2.png) [@jmorahan](https://community.letsencrypt.org/u/jmorahan)\
**Post date:** [March 18, 2018, 1:13pm UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/10 "2018-03-18T13:13:41Z")

</div>

We can probably figure it out if you tell us the domain name…

---

<div class="post-metadata">

**Author:** ![Carolyn](https://avatars.discourse-cdn.com/v4/letter/c/3ab097/32.png) [@Carolyn](https://community.letsencrypt.org/u/Carolyn)\
**Post date:** [March 18, 2018, 1:26pm UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/11 "2018-03-18T13:26:37Z")

</div>

Well all my servers are at the domain [haapie.com](http://haapie.com)  
so for example, i have [sandbox.fr.haapie.com](http://sandbox.fr.haapie.com)

---

<div class="post-metadata">

**Author:** ![jmorahan](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jmorahan/32/1873_2.png) [@jmorahan](https://community.letsencrypt.org/u/jmorahan)\
**Post date:** [March 18, 2018, 1:42pm UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/12 "2018-03-18T13:42:52Z")

</div>

I can’t seem to connect to the sandbox subdomain, but it looks like [haapie.com](http://haapie.com) is using Apache.

So the correct instructions would be [here](https://certbot.eff.org/lets-encrypt/ubuntuxenial-apache).

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [April 17, 2018, 1:43pm UTC](https://community.letsencrypt.org/t/not-receiving-email-alerts-anymore/56843/13 "2018-04-17T13:43:08Z")

</div>

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