HomeLab SSL certificates for FREE with minimal effort

preview_player
Показать описание
In this video we use Nginx Proxy Manager, DuckDNS , Let's Encrypt and our HomeLab to setup SSL certificates. We use DuckDNS to avoid the cost of a domain making this free of cost and all of the software using is FOSS. We use Docker to keep thing simple and it is mostly just copy and paste from official documentation.

Рекомендации по теме
Комментарии
Автор

Still one of the BEST NPM walkthrough's I've seen.

QEDAGI
Автор

best tutorial ive seen so far. congrats...

lms
Автор

This is an awesome tutorial and I am thankful that I found it. I was able to recreate everything in just few minutes and now it is working without any problems at all. Clear instructions with a nice flow that it is really easy to follow, thanks a lot.

makskav
Автор

Great video, this has been really helpful and interesting in getting a base lab setup for SSL certs. I'm excited to dive in and look at setting up and generating internal certs for my lab in the future.

purplepurrpurrin
Автор

Really interesting! Thanks for the guide!

zippi
Автор

Great video! Im an absolut newbie and want to set up my first ever Rasberry Pi homelab and have been researching for the oast month on how to set things up. This solves the question on how to get ssl certs for vaultwarden without opening any ports. Additionally, I want to set up Pi Hole (as you showed) but also unbound as a local recursive DNS. Will this somehow interfere with the local dns challange you set up with DuckDNS? (Sorry for the stupid question. Im still very unsure with all the IT-Terms and get cofused with how everything interacts with each other)

noad
Автор

this was the simplest and working nginx tutorial among a few, thank you!

ggcub
Автор

Really nice video.Do you know if the ssl certs is auto renewed by nginx proxy manager? I have not seen any option about it. Thanks for this kind of content.

michelecicozzi
Автор

Amazing, very useful video and clear step. one question, certificate will automatically renew?

fahmi
Автор

Hey there, this might be a silly question but can you explain why you set your duckDNS domain to a local IP address? If you want to access a service over the internet, how would a user in another place resolve that IP? I'm very much a beginner trying to learn homelabbing and networking.

Is this meant only to provide certificates for local use? Or maybe i'm misunderstanding. Thanks a bunch!

HowlYeYe
Автор

I got SSL to work only for ngnix, I have a pretty simple setup with proxmox running my containers for my other servers. and I have a container with docker installed where ngnix lives, would I have to install certbot in all of my other containers in proxmox to have this work as well or am I missing something?

nigelnovelo
Автор

Will this work for remote access like sharing jellyfin with family or is this only for your LAN?

Edit: nevermind I just heard the beginning of the video again, but how would you go about configuring for public access?

thedinotamergaming
Автор

Hello, Thanks for a Great video and amazing explanation. I have questions though..

Without the internet, will I still be having certs on my LAN services? What about the domain name? This I asked because of your previous video on pihole setup with local dns. How can I get the best of both worlds, local and external access with ssl?


Are the certs going to be updated automatically?

maxxwellwalt
Автор

Thanks for that video. It helped me a lot with direction. I could even configure NextCloud based on the same container wwith Portainer as Nginx Proxy Manager, but at cost of 4-5 hours :)

ushinary
Автор

very nice video. thanks you bro, you really help. this tutorial is work nicely and very detail step

harrisjefferson
Автор

Thx for this great Video now its working for me

jensg.
Автор

Video is very well explained ! but when put "*" 13:12 in domains not work, not permit, any tip?

alexandretravi
Автор

Awesome tutorial i only didn't got the proxy not working i put the ip of the container where NPM is running in the dns record from duckdns but when i create a proxy in NPM and i click on it i get a error that the server can not be found but when i use the normal ip of the server it does work (same is true when i add NPM to the proxy list and try with my domain from duckdns) Edit:my first comment disappeared so i hope this one stays. Edit 2: if you encounter the same problem as me so following the tutorial and not able to reach the server. turn off DNS Rebind protection or whitelist them so your router lets them through. well come to the 7 hour story of my life all because of DNS rebind protection :P

oosterlingeieren
Автор

18:50 can you explain why for this particular entry you're leaving the scheme set to "http" instead of https and you're not enabling "Force SSL"?

miique
Автор

dumb question and also just learning all this can I install an lxc container of nginx proxy manager without installing docker and this still work?

ndtemple