[users@httpd] TLS handling with reverse proxy

I have a successful non-apache reverse proxy server working behind a non-tls public-facing apache server. What do I have to do to use TLS with Let's Encrypt certs managed certificates? I have "normal" managed TLS servers working fine, but the reverse proxy TLS settings are a mystery to me. Thank

Re: [users@httpd] TLS handling with reverse proxy

I may be using the setup you describe. I have Webmin to manage services (independent of Apache) and access it over https (using a (browser-trusted) certificate I made). Webmin could be accessed with either the : ending or a subdomain (via reverse-proxing). But now I can only access via : , so

Re: [users@httpd] TLS handling with reverse proxy

On Sun, Aug 30, 2020 at 10:37 Yuma Technical Inc. wrote: > I may be using the setup you describe. I have Webmin to manage services > ... Thanks, that helps. My data flow is a bit different, but every little piece of a working solution is a step in the right direction! Best regards: -Tom

Re: [users@httpd] TLS handling with reverse proxy

On Sun, Aug 30, 2020 at 11:12 Tom Browder wrote: > On Sun, Aug 30, 2020 at 10:37 Yuma Technical Inc. > wrote: > >> I may be using the setup you describe. I have Webmin to manage services >> > ... > Can you tell me how the _default_ works with SNI virtual hosts? -Tom

Re: [users@httpd] TLS handling with reverse proxy

On Mon, Aug 31, 2020 at 07:10 Tom Browder wrote: > On Sun, Aug 30, 2020 at 11:12 Tom Browder wrote: > >> On Sun, Aug 30, 2020 at 10:37 Yuma Technical Inc. < >> yumatechni...@gmail.com> wrote: >> >>> I may be using the setup you describe. I have Webmin to manage services >>> >> ... >> > > Can yo

Re: [users@httpd] TLS handling with reverse proxy

Hi Don’t forget the “:” between host and port. If you want, even *:* will allow any server on any port… So I guess ${DOMAIN}.${TLD}:${PORT} > On Aug 31, 2020, at 8:19 AM, Tom Browder wrote: > > > > On Mon, Aug 31, 2020 at 07:10 Tom Browder > wrote: > On Sun,

Re: [users@httpd] TLS handling with reverse proxy

On Mon, Aug 31, 2020 at 14:18 Yuma Technical Inc. wrote: > Don’t forget the “:” between host and port. If you want, even * > So I guess ${DOMAIN}.${TLD}:${PORT} > That is part of the macro definition. The vhost details come after that and its format is correct as you showed it. I think I'm get

Re: [users@httpd] TLS handling with reverse proxy

Hi In my case, I use Webmin. It is written in perl and the HTTP server is Miniserv. One can set the listen port number, whether to use HTTPS, and many other parameters, in a INI file. So I do have any code to show you for this. If you ask for a specific file, I can show that, otherwise I’m