# AWS Lightsail - Name does not end in a public suffix

**URL:** <https://community.letsencrypt.org/t/aws-lightsail-name-does-not-end-in-a-public-suffix/85927>\
**Category:** Help\
**Created:** [February 12, 2019, 12:13pm UTC](https://community.letsencrypt.org/t/aws-lightsail-name-does-not-end-in-a-public-suffix/85927 "2019-02-12T12:13:01Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![LordLiverpool](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/lordliverpool/32/29832_2.png) [@LordLiverpool](https://community.letsencrypt.org/u/LordLiverpool)\
**Post date:** [February 12, 2019, 12:13pm UTC](https://community.letsencrypt.org/t/aws-lightsail-name-does-not-end-in-a-public-suffix/85927/1 "2019-02-12T12:13:01Z")

</div>

Hello Let’s Encrypt

I was following this AWS Tutorial on how to install an SSL certificate.

[https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-using-lets-encrypt-certificates-with-wordpress](https://lightsail.aws.amazon.com/ls/docs/en/articles/amazon-lightsail-using-lets-encrypt-certificates-with-wordpress)

But when I got step 3 part 6 I got an error message (see below)

I entered my email address and verified it with the Electronic Frontier Foundation  
I agreed to the terms and conditions

What have I done wrong? .com is a public suffix

Any help is appreciated.

Thanks

My domain is: [http://energysrs.com](http://energysrs.com)

I ran this command: `sudo certbot -d $DOMAIN -d $WILDCARD --manual --preferred-challenges dns certonly`

It produced this output: `The request message was malformed :: Error creating new order :: Name does not end in a public suffix`

My web server is (include version): `Server version: Apache/2.4.34 (Unix) Server built: Jul 30 2018 17:17:22`

The operating system my web server runs on is (include version):`Linux 4.4.0-1065-aws x86_64`

My hosting provider, if applicable, is: `AWS - Lightsail - Bitnami WordPress Instance`

I can login to a root shell on my machine (yes or no, or I don’t know): `yes via Lightsail SSH terminal`

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): `no`

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

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [February 12, 2019, 12:15pm UTC](https://community.letsencrypt.org/t/aws-lightsail-name-does-not-end-in-a-public-suffix/85927/2 "2019-02-12T12:15:08Z")

</div>

What are `$DOMAIN` and `$WILDCARD` set to?

---

<div class="post-metadata">

**Author:** ![LordLiverpool](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/lordliverpool/32/29832_2.png) [@LordLiverpool](https://community.letsencrypt.org/u/LordLiverpool)\
**Post date:** [February 12, 2019, 12:17pm UTC](https://community.letsencrypt.org/t/aws-lightsail-name-does-not-end-in-a-public-suffix/85927/3 "2019-02-12T12:17:50Z")

</div>

Thanks for the fast reply!

`echo $DOMAIN && echo $WILDCARD energysrs.com *.DOMAIN`

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [February 12, 2019, 12:20pm UTC](https://community.letsencrypt.org/t/aws-lightsail-name-does-not-end-in-a-public-suffix/85927/4 "2019-02-12T12:20:45Z")

</div>

`*.DOMAIN` isn’t a public suffix. It’s supposed to be `*.energysrs.com`.

By the way, relying on manual validation is problematic. It means the certificate can’t be automatically renewed and you have to do it by hand every couple months.

That tutorial is apparently using Ubuntu; your domain is using Cloudflare’s DNS. You can install the Certbot Cloudflare DNS plugin with `sudo apt-get install python3-certbot-dns-cloudflare` and use it to validate with less copying and pasting and more automatic renewal. (You still have to fix the domain, though.)

[https://certbot-dns-cloudflare.readthedocs.io/en/stable/](https://certbot-dns-cloudflare.readthedocs.io/en/stable/)

---

<div class="post-metadata">

**Author:** ![LordLiverpool](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/lordliverpool/32/29832_2.png) [@LordLiverpool](https://community.letsencrypt.org/u/LordLiverpool)\
**Post date:** [February 12, 2019, 12:39pm UTC](https://community.letsencrypt.org/t/aws-lightsail-name-does-not-end-in-a-public-suffix/85927/5 "2019-02-12T12:39:43Z")

</div>

@mnordhoff thanks for your help, it's appreciated.

Sorry for making an obvious syntax error, my apologies. I'll pay closer attention from now on.

Thank you for the suggestion of using the Certbot Cloudflare DNS plugin.  
I'm tempted to move the domain to AWS Route 53 to manage the DNS there.  
If so would I be able to set-up auto renewal?

A quick Google reveals:

> [@Renewal on Amazon AWS / Lightsail](https://community.letsencrypt.org/t/renewal-on-amazon-aws-lightsail/66855):
>
> H…

> **[SSL for AWS Lightsail Wordpress](https://medium.com/pixelpassion/ssl-for-aws-lightsail-wordpress-8053359a774f)**
>
> In my previous blog article, I wrote about installing a Wordpress blog on AWS Lightsail.

> **[ACME Client Implementations - Let's Encrypt](https://letsencrypt.org/docs/client-options/)**
>
> Last updated: Jul 22, 2023 | See all Documentation Let’s Encrypt uses the ACME protocol to verify that you control a given domain name and to issue you a certificate. To get a Let’s Encrypt certificate, you’ll need to choose a piece...

Am I on the right track?

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [February 12, 2019, 12:41pm UTC](https://community.letsencrypt.org/t/aws-lightsail-name-does-not-end-in-a-public-suffix/85927/6 "2019-02-12T12:41:56Z")

</div>

> [@LordLiverpool](#):
>
> I’m tempted to move the domain to AWS Route 53 to manage the DNS there.  
> If so would I be able to set-up auto renewal?

Certbot also has a Route 53 plugin. 🙂

[https://certbot-dns-route53.readthedocs.io/en/stable/](https://certbot-dns-route53.readthedocs.io/en/stable/)

---

<div class="post-metadata">

**Author:** ![LordLiverpool](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/lordliverpool/32/29832_2.png) [@LordLiverpool](https://community.letsencrypt.org/u/LordLiverpool)\
**Post date:** [February 12, 2019, 12:43pm UTC](https://community.letsencrypt.org/t/aws-lightsail-name-does-not-end-in-a-public-suffix/85927/7 "2019-02-12T12:43:48Z")

</div>

@mnordhoff

You’re very helpful, thank you! 😄

---

<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:** [March 14, 2019, 12:43pm UTC](https://community.letsencrypt.org/t/aws-lightsail-name-does-not-end-in-a-public-suffix/85927/8 "2019-03-14T12:43:53Z")

</div>

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