-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
thoughts on the project #9
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I started out with your traefik v2 https ssl localhost. This uses makecert to make your own local certs. The issue with this setup, is an invalid cert which will constantly be warned by browser is not valid. You can still accept though.
The alternative to this is what Techno Tim did using Traefik + cloudflare local dns + lets encrypt. So what his method does is allow to setup a reverse proxy (same one like yours), but have a working valids lets encrypt cert for https which can be used locally for a local homelab setup without exposing to the internet.
https://www.youtube.com/watch?v=n1vOfdz5Nm8
The alternative to that is Wolfgang's approach but using Nginx proxy manager
https://www.youtube.com/watch?v=qlcVx-k-02E
So you can either go with Nginx Proxy Manager or traefik. But both managed to gets working https valid certs for local homelab setup using lets encrypt.
Wolfgang uses either a paid domain or free one e.g. duckdns. Whereas technotim uses similar to your approach Heziode, a local domain e.g. dashy.local.lan Either would work fine for local homelab setup.
Anyway appreciate Heziode's project since i started out with it, but i came across 2 good options that resolved the valid https cert issue, so thought i'd mention here for others wanting to setup for local homelab but wondering how to improve upon this existing project.
The text was updated successfully, but these errors were encountered: