nextcloud / nextcloud/nextcloudpi

Let's Encrypt DNS-01 challenge support

Open
#1,899 0 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
2.9k
Forks
318
PR merge metrics
No merged PRs in 30d

Description

Description

Please add the option to use letsencrypt with the dns challenge feature. I don't have any ports open in my home network but want to use a real dns name and certificate.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name any files, tests, or entry points. Start by locating the existing Let's Encrypt or certificate setup and determine how DNS-01 providers would be configured; done means a real DNS name can obtain and renew a certificate without open network ports.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
devops, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.