nextcloud / nextcloud/nextcloudpi
Letsencrypt without Port 80 Setup
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.9k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
I have found a script that possibly can be ported to nextcloudpi for using letsencrypt and duckdns when port 80 is blocked by ISP. I am no coder, but I have looked through it and it looks plausible.
The script is found at https://github.com/lukas2511/dehydrated/blob/master/dehydrated
The author has a tutorial for the project/script found here.
Is there any way this is possible to integrate into the ncp config?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked dehydrated script and the linked Home Assistant/DuckDNS tutorial to understand the proposed certificate flow when port 80 is blocked. Then inspect the NextcloudPi configuration entry points for existing Let's Encrypt support; done would mean a documented, integrated path for this setup, with its configuration behavior and limitations tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100