Remove (legacy) LetsEncrypt email field
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
- LetsEncrypt email notifications have ended as of June 4, 2025 – https://letsencrypt.org/2025/01/22/ending-expiration-emails
- The UI still requires the email field:
LetsEncrypt email is required when certificate type is letsencrypt
Describe the solution you'd like
Remove the email field for LetsEncrypt
Describe alternatives you've considered
An alternative is to use a placeholder email @example.com since this is not used by LetsEncrypt anymore
Additional context
Happy to create a PR if you agree with the removal!
Will you send a PR to implement it?
Maybe, need help
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 searching the repository for the validation text "LetsEncrypt email is required when certificate type is letsencrypt" and the LetsEncrypt certificate form. Trace the UI and validation path, then remove the email requirement for LetsEncrypt and verify that certificate creation no longer needs that field.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100