GithubHelp home page GithubHelp logo

csmith / docker-letsencrypt-lexicon Goto Github PK

View Code? Open in Web Editor NEW
10.0 2.0 3.0 18 KB

Docker container to automatically obtain letsencrypt certificates using the lexicon DNS library

License: MIT License

Shell 86.96% Dockerfile 13.04%
docker docker-automatic-proxy letsencrypt lexicon

docker-letsencrypt-lexicon's Issues

ERROR: An error occurred while sending get-request to http://cert.int-x3.letsencrypt.org/ (Status 301)

I'm getting this error and all the certificates are now invalid.
Hope it's a simple fix.
Thanks


+ Challenge is valid!
 + Requesting certificate...
 + Checking certificate...
 + Done!
 + Creating fullchain.pem...
  + ERROR: An error occurred while sending get-request to http://cert.int-x3.letsencrypt.org/ (Status 301)

Details:
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>

RSA keys instead of EC Keys

Thanks for your Docker and it is a great idea and implementation!

But the docker currently generates EC Keys for the certs. Is there anyway to have regular RSA keys instead?

It makes it much easier for importing the certs and keys to other apps......

Certificate doesn't seems full

Hello,

I'm trying to get my certificates using your docker image.

I put my lexicon account, and my domains.txt seems to be taken.

When starting the container, some directory are created.
( archive, certs, accounts )
So it looks like my parameters are well passed to the container.

But inside certs, I found a directory name with my domain.
And inside that some files a generated :

-rw------- 1 root root  538 Oct 11 10:24 cert-1539246254.csr
-rw------- 1 root root    0 Oct 11 10:24 cert-1539246254.pem
-rw------- 1 root root  359 Oct 11 10:24 privkey-1539246254.pem

But the cert-*.pem is empty.

When i'm using certbot with the manual generation of my certificate, here's what I obtain:

-rw-r--r-- 1 root root 2179 Oct 10 17:19 cert1.pem
-rw-r--r-- 1 root root 1647 Oct 10 17:19 chain1.pem
-rw-r--r-- 1 root root 3826 Oct 10 17:19 fullchain1.pem
-rw-r--r-- 1 root root 1708 Oct 10 17:19 privkey1.pem

So with certbot the files are much bigger (and I have 4 of them), wherease with your docker, I get 3 files, and one of them is empty.

So I suppose that the certs generation as failed, but how can I get sure of that ?
Is there any log of action somewhere ?

Add support for wildcard certs

At the moment trying to request a wildcard cert results in the following error:

+ ERROR: An error occurred while sending post-request to https://acme-staging.api.letsencrypt.org/acme/new-authz (Status 400)

Details:
{
  "type": "urn:acme:error:malformed",
  "detail": "Error creating new authz :: Wildcard names not supported",
  "status": 400
}

I think we probably need to update our dependencies to support ACMEv2

Fake LE Intermediate X1 - Cert Regeneration

Hi,

During testing I set the environment variables to:

    environment:
      - [email protected]
      - STAGING=true # any value equals true. Leave blank for false
      - ACCEPT_CA_TERMS=true # any value equals true. Leave blank for false
      - PROVIDER=cloudflare
      - [email protected]
      - LEXICON_CLOUDFLARE_TOKEN=supersecrettoken

The test cert was issued and I tested the website with it. It works but it's signed by Fake LE Intermediate X1

I thought that I just had to amend the environment variable of stanging to be empty and re-compose but the certs don't regenerate against a non-stages LE CA.

    environment:
      - [email protected]
      - STAGING= # any value equals true. Leave blank for false
      - ACCEPT_CA_TERMS=true # any value equals true. Leave blank for false
      - PROVIDER=cloudflare
      - [email protected]
      - LEXICON_CLOUDFLARE_TOKEN=supersecrettoken

any help greatly appreciated.

Thanks,

Tom

Lexicon Update

Would you mind updating to a later version of lexicon?

Apparently, the container doesn’t support mythicbeasts yet:
3C211669-0671-4B27-9B23-E8BEFD4C43E6

Although it does look to be supported according to lexicon.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.