bunkerity / bunkerity/bunkerweb

[FEATURE] allow letsencrypt passthrough when bunkerweb itself did not send a request

Open
#3,386 7 comments 1 reaction 1 assignee Claimed by @TheophileDiot View on GitHub
core enhancement
Dominant language
Python
Stars
10.9k
Forks
643
Avg merge
1d 10h
Merged PRs (30d)
42

Description

### What's needed and why?

Hi,

In some environments, where your internal connections will directly route to a System for performance reasons, you still want to have a valid letsencrypt certificate. For this to work, bunkerweb could passthrough "foreign origin let's encrypt ACME chalenges" directly to the upstream server.

in summary:

normal usage:
bunkerweb -> letsencrypt -> ACME -> bunkerweb

internal let's encrypt usage:

internal webserver -> let's encrypt -> ACME -> bunkerweb does not know it requested -> internal webserver

kind regards

Mike

### Implementations ideas (optional)

_No response_

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.