I've been playing with Pingora to create a reverse proxy that connects backend HTTP or HTTPs service to a single HTTPs frontend (similar to what is generally done with Nginx) serving distinct SSL certificates (using SNI and the host header) for each backend service.
* with an SNI and Host header of somedomain.com, you will be served an SSL certificate to somedomain.com and a proxied connection to http://127.0.0.1:4000.
* with an SNI and Host header of one.one.one.one, you will be served an SSL certificate to one.one.one.one and a proxied connection to https://one.one.one.one.
In this example, if you connect to https://127.0.0.1:4430:
* with an SNI and Host header of somedomain.com, you will be served an SSL certificate to somedomain.com and a proxied connection to http://127.0.0.1:4000.
* with an SNI and Host header of one.one.one.one, you will be served an SSL certificate to one.one.one.one and a proxied connection to https://one.one.one.one.
Note: Pingora is a network services crate that Cloudflare recently opensourced, see https://news.ycombinator.com/item?id=39535969 https://news.ycombinator.com/item?id=39551115