[GH-ISSUE #107] Using Wildcard Let's Encrypt certificates with go-http-tunnel #58

New issue

Closed

opened 2026-05-05 10:59:13 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 10:59:13 -06:00

Owner

Originally created by @1ubuntuuser on GitHub (Nov 5, 2019).
Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/107

HTTP/2 from end to end is AMAZING. Although having my own self-signed certificates is fine for setting up, don't really want to tell those visiting my webui they have to accept a dodgy-looking certificate.

My next move was to use a certbot with the "certonly" flag to create some nice wildcard certificates authenticated with my domain. Done!

Only issue is, I know let's encrypt certificates expire. Will I have to recreate all my client certificates every time I renew the wildcard certificate?

In an ideal world, I would use my own self signed certificate from client to server and use the officially signed certificate from server to web browser. Not sure if that's possible though.

Any help would be much appreciated!

Originally created by @1ubuntuuser on GitHub (Nov 5, 2019). Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/107 HTTP/2 from end to end is AMAZING. Although having my own self-signed certificates is fine for setting up, don't really want to tell those visiting my webui they have to accept a dodgy-looking certificate. My next move was to use a certbot with the "certonly" flag to create some nice wildcard certificates authenticated with my domain. Done! Only issue is, I know let's encrypt certificates expire. Will I have to recreate all my client certificates every time I renew the wildcard certificate? In an ideal world, I would use my own self signed certificate from client to server and use the officially signed certificate from server to web browser. Not sure if that's possible though. Any help would be much appreciated!