Thank you for saving my sanity, I was watching another tutorial and it was so bloated and confusing, this was straight to the point and had me up and running in minutes! Subbed
I'm glad it helped, and be patient. A lot of my content is long and detailed. I like to make sure that beginners can learn as they try to bring up new services. Mostly learn from my mistakes. ;-) Thanks for the sub.
If you have your own domain, you'd setup a wildcard A record (like *.example.com points to your public IP). If your public IP changes, then you'll need to setup a watcher application (often a docker version already available) that will update your IP to your registrar as needed.
Thank you for this tutorial. Do you know if this will work behind 2 routers? I have 1 Huawei EG8145V5 (ISP Provided / CGNAT) and a TP-Link Archer C24 (where my home server is connected). I haven't tried dismantling my setup yet, but I probably may do it to test at a later time.
So, I think it may be able to call out from double-nat, but not sure you'll be able to get back in unless you control both and can chain your port-forwarding through as needed. Definitely check out solutions for double-NAT if you can't.
buy a static ip from your ISP or you can use tailscale or if you strictly want to go selfhosted then pritunl or netmaker on vultr you can choose from any of these option 👍
@@kingofgames-jj7wl This will work, but not all ISPs offer such a thing. There are options, as stated - TailScale, or run your own DigitalOcean server for $5 a month, and setup wireguard as a server on it, then you reach out from inside your network to it. Essentially what TailScale does, but more manually.
@@RedScreen if you have a static ip, you don’t need ddns. But for a lot of folks the static ip isn’t possible. In the US at least, a static IP from most ISPs is reserved for businesses and business level service. So this is a less expensive option for those making a simple homeland.
Hey I have a question If I buy a physique servers and want to sell domains name like GoDaddy, Where and how I can be a domain provider , I see videos for reselling domain and Host or cloud but I don`t want to be a reseller I want to be the first Provider of domain , I hope if you cane advice me for that.... thanks again
I don't have any information on how to do that. I think your search term might be "how to become a top level domain tld provider". I imagine there is some extreme expense in doing that, but I don't really know.
so for me it didnt work at all if it was for portainer or docker non of it would let my duckdns url go on do i need to open some port that i didnt know of ? bcs i did everything but nothing succeeded
Yes, you still need to open ports 80 and 443 and forward them to the reverse proxy server on your network. DuckDNS just provides a URL that will try to update according to your public IP. The other thing to watch out for is if you have Double NAT from your ISP, you may need some other stuff setup. But DucDNS doesn't punch a hole through your firewall.
So, if your router runs on port 80, make sure you are forwarding traffic to port 80 from the WAN to the LAN IP of your NGinX Proxy Manager host. You may have to move your router web interface off of port 80.
You can use a DuckDNS address, and setup a Tunnel with something like Wireguard and not open any ports inside your network, or you can simply pass the traffic for 80 and 443 to a single machine running a reverse proxy, and let that push the traffic around your network (to different servers / services you run) as needed.
very cool but you don't need to create multiple duckdns subdomains like that. just create a single duckdns subdomain (myserver.duckdns.org) and then use sub-subdomains in your reverse proxy (plex.myserver.duckdns.org, meshctrl.myserver.duckdns.org). can use a single wildcard cert for your subdomain as well (*.myserver.duckdns.org).
Thank you for saving my sanity, I was watching another tutorial and it was so bloated and confusing, this was straight to the point and had me up and running in minutes! Subbed
I'm glad it helped, and be patient. A lot of my content is long and detailed. I like to make sure that beginners can learn as they try to bring up new services. Mostly learn from my mistakes. ;-) Thanks for the sub.
Thank you so much. You really showed a full solution with which one can create reliable connection to Home Lab, Greate.
You're welcome!
@@AwesomeOpenSource did you ever try doing duckdns subdomains setup with caddy? thnx
Thanks for making this video! It’s very helpful and informative!
Glad you enjoyed it!
Thank you for this comprehensive guide. By the way have you made a video that covers how to do it with own domain as stated here 5:16?
If you have your own domain, you'd setup a wildcard A record (like *.example.com points to your public IP). If your public IP changes, then you'll need to setup a watcher application (often a docker version already available) that will update your IP to your registrar as needed.
Thank you for this tutorial. Do you know if this will work behind 2 routers? I have 1 Huawei EG8145V5 (ISP Provided / CGNAT) and a TP-Link Archer C24 (where my home server is connected). I haven't tried dismantling my setup yet, but I probably may do it to test at a later time.
So, I think it may be able to call out from double-nat, but not sure you'll be able to get back in unless you control both and can chain your port-forwarding through as needed. Definitely check out solutions for double-NAT if you can't.
What do you suggest for people behind a CGNAT (Double NAT situation) ?
Let me do some digging on that.
buy a static ip from your ISP or you can use tailscale or if you strictly want to go selfhosted then pritunl or netmaker on vultr you can choose from any of these option
👍
@@kingofgames-jj7wl This will work, but not all ISPs offer such a thing. There are options, as stated - TailScale, or run your own DigitalOcean server for $5 a month, and setup wireguard as a server on it, then you reach out from inside your network to it. Essentially what TailScale does, but more manually.
just ask your service provider if they can pull you out of the nat pool for free. what is the point of a ddns if you buy a static ip?
@@RedScreen if you have a static ip, you don’t need ddns. But for a lot of folks the static ip isn’t possible. In the US at least, a static IP from most ISPs is reserved for businesses and business level service. So this is a less expensive option for those making a simple homeland.
Thank you :))
You're welcome!
Hey I have a question If I buy a physique servers and want to sell domains name like GoDaddy, Where and how I can be a domain provider , I see videos for reselling domain and Host or cloud but I don`t want to be a reseller I want to be the first Provider of domain , I hope if you cane advice me for that.... thanks again
I don't have any information on how to do that. I think your search term might be "how to become a top level domain tld provider". I imagine there is some extreme expense in doing that, but I don't really know.
@@AwesomeOpenSource yes that`s what I mean . thanks
5:10 Could you do a tutorial on using custom domains with DuckDNS?
Are you talking like myapp1.myhome.duckdns.org?
so for me it didnt work at all if it was for portainer or docker non of it would let my duckdns url go on do i need to open some port that i didnt know of ? bcs i did everything but nothing succeeded
Yes, you still need to open ports 80 and 443 and forward them to the reverse proxy server on your network. DuckDNS just provides a URL that will try to update according to your public IP. The other thing to watch out for is if you have Double NAT from your ISP, you may need some other stuff setup. But DucDNS doesn't punch a hole through your firewall.
instead of congratulations it took me to the router … how safely I can open a path to the destination?
So, if your router runs on port 80, make sure you are forwarding traffic to port 80 from the WAN to the LAN IP of your NGinX Proxy Manager host. You may have to move your router web interface off of port 80.
Great vid thanks
Glad you enjoyed it.
Love it
Thank you
wait, we dont need to open router ports ?
You can use a DuckDNS address, and setup a Tunnel with something like Wireguard and not open any ports inside your network, or you can simply pass the traffic for 80 and 443 to a single machine running a reverse proxy, and let that push the traffic around your network (to different servers / services you run) as needed.
this is the first like for your video pro
And I appreciate it.
someone who understands about Duckdnds please 😭😭 i nedddd
If you need help jump over to discuss.opensourceisawesome.com and ask your question. We'll see if we can help you.
I must admit, your videos have too much talk for my liking. Good content otherwise. Thanks for sharing
I no concise.
very cool but you don't need to create multiple duckdns subdomains like that. just create a single duckdns subdomain (myserver.duckdns.org) and then use sub-subdomains in your reverse proxy (plex.myserver.duckdns.org, meshctrl.myserver.duckdns.org). can use a single wildcard cert for your subdomain as well (*.myserver.duckdns.org).
Nice tip! Kinda killing my follow up videos here! :-P