Error issuing Let's Encrypt certificate from Dokku.

I installed and use a Docker-based PaaS tool (?) called Dokku in my AWS EC2 instance. Recently, a Let's Encrypt plug-in came out and I'm trying to use it to issue a certificate. I've tried several times, but the Invalid character in DNS name error continues to occur in the certificate issuance as shown below. If you have used Let's Encrypt before, please answer if you know how to solve this error.

For your information, the usage environment is as follows.

AWS EC2 t2.micro Instance - Ubuntu 14.04.4 LTS
The domain to which the certificate is issued: shipped.c.youngbin.xyz

The name server is using Cloudflare and is using the following settings.

Cloudflare SSL: Using Flexible SSL
Redirect to http://youngbin.xyz/* -> https://youngbin.xyz/*

A / *.c / <EC2 instance IP>  
A /c / <EC2 instance IP>  
A / youngbin.xyz / 192.30.252.153(GitHub Pages IP)  
A / youngbin.xyz / 192.30.252.154(GitHub Pages IP)  
CNAME / www / youngbin.xyz

ubuntu@ip-172-31-24-252:~$ dokku --v letsencrypt shipped
=====> Let's Encrypt shipped...
-----> Updating letsencrypt docker image...
latest: Pulling from m3adow/letsencrypt-simp_le
4d06f2521e4f: Already exists 
a3ed95caeb02: Already exists 
8d87d7d66444: Already exists 
87187c773fd1: Already exists 
Digest: sha256:66269a4cc647c9847a7f4f8ba39ba98caeb3b1b824d4f28ccb7dcc7b21351f25
Status: Image is up to date for m3adow/letsencrypt-simp_le:latest
       done
-----> Enabling ACME proxy for shipped...
-----> Getting letsencrypt certificate for shipped...
        - - Domain 'shipped.c.youngbin.xyz/'
darkhttpd/1.11, copyright (c) 2003-2015 Emil Mikulic.
listening on: http://0.0.0.0:80/
2016-03-23 04:43:59,717:INFO:__main__:1202: Generating new account key
2016-03-23 04:44:00,798:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
2016-03-23 04:44:02,648:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
2016-03-23 04:44:03,491:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
2016-03-23 04:44:04,461:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): letsencrypt.org
2016-03-23 04:44:04,639:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
2016-03-23 04:44:05,564:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
ACME server returned an error: urn:acme:error:malformed :: The request message was malformed :: Error creating new authz :: Invalid character in DNS name


Debugging tips: -v improves output verbosity. Help is available under --help.
-----> Certificate retrieval failed!
-----> Disabling ACME proxy for shipped...
       done
ubuntu@ip-172-31-24-252:~$

docker letsencrypt aws ec2 dokku

2022-09-22 15:26

1 Answers

If you look at - Domain's shipped.c.youngbin.xyz/' in the log, there is / in the back, isn't it because of this?

2022-09-22 15:26

If you have any answers or tips

Popular Tags

python x 4647

android x 1593

java x 1494

javascript x 1427

c x 927

c++ x 878

ruby-on-rails x 696

php x 692

python3 x 685

html x 656