NginxProxyManager / NginxProxyManager/nginx-proxy-manager
geoip2 blocks renewal of the certificate (via http)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
I had some problems renewing my certificate over HTTP. After a long search, I finally found the solution: GeoIP2.
GeoIP2 works perfectly, though it's limited to Germany for me. Unfortunately, this means Let's Encrypt no longer works with HTTP.
Is there any way to define an exception?
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by reproducing HTTP certificate renewal with GeoIP2 enabled and inspect how access restrictions interact with the Let's Encrypt renewal path. Done means a documented or configurable exception allows renewal while GeoIP2 remains enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100