Skip to content
This repository was archived by the owner on Apr 14, 2025. It is now read-only.
This repository was archived by the owner on Apr 14, 2025. It is now read-only.

find a way to survive connection failures to Let's Encrypt #9

Description

@anarcat

one issue with having the dcomms server offline is that they might be cut off from the Let's Encrypt certificate authority and, after a while (< 90 days), their certificates will expire.

renewing certs with let's encrypt is pretty hard in difficult network conditions. you not only need to be able to reach them, but they need to reach you and from multiple vantage points on the internet.

so it might be worth looking at alternatives. some ideas:

  • get a certificate with a longer lifetime, maybe from a commercial provider (Tor uses Digicert for the web browser signing, Fastly use Global Sign, for what that's worth)
  • use a DNS-01 challenge, as DNS has a better chance of getting through censorship and high latency issue (e.g. it might work better with a satellite uplink)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions