cloudflare-ddns VS cloudflared

For anyone following, this was due to user error in that DDNS was not up to date. For reference, https://github.com/timothymiller/cloudflare-ddns

If you want to reach them online, think about using something like this: https://github.com/timothymiller/cloudflare-ddns, this will automaticly update your A records. Or try Cloudflare Tunneling: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps

Try using this container instead. You can update the A record of your domain to your IP dynamically and use a CNAME for each subdomain so you don’t have to worry about them not resolving when your IP changes.

Can you explain the difference between that and this? https://github.com/timothymiller/cloudflare-ddns

I'm out of ideas on this one, I especially don't understand why the nginx container works and others dont. Besides that I'm interested in other solutions that don't route my whole traffic over one company and limit my traffic/what I am allowed to do and what not. Would a dynamic dns updater also work for my use case? Something like cloudflare-ddns?

My recommended roadmap for thing to host is: 1. ssh access * with certificates only and fail2ban config 2. local pihole DNS server * learn how to set up your router and devices to use pihole as DNS 3. local jellyfin * no encryption, no external access, just a simple local network service * Create a domain in pihole, that points to your local jellyfin service 4. a ddns-service like cloudflare-ddns * buy a domain and use ddns to point it to your IP 5. nginx-proxy-manager * enable port-forwarding in your router and obtain a lets-encrypt wildcard-cert for your domain * Create a docker network and add npm, jellyfin, and all other web services that you want to access via your domain * Create a proxy host for each service, give every service a unique subdomain, and use your wildcard cert to enable SSL/TLS for all your services * add all those subdomains to your ddns * use pihhole to point the subdomains to your local IP

Tailscale recently introduced funnel which is currently in beta and has bandwidth limits so it might work, but personally I'd use a dynamic DNS service like cloudflare-ddns

Cloudflare Tunnel - Excellent free option. Nicely integrates tunneling with the rest of Cloudflare's products, which include DNS and auto HTTPS. Client source code is Apache 2.0 licensed and written in Golang.

I run a RaspberryPi 3 with FreeBSD 13 booting off an SD card and a USB SSD for storage [1]. Coincidentally today (1/7/2024) is its one year anniversary.

It runs a jail with my single user GotoSocial ActivityPub server [2] reasonably well with cloudflared [3] handling incoming traffic and acting as CDN to take some of the load. Originally it was only using an SD card, but there was too much IO contention so a USB-SSD adapter is used to offload the IO.

I choose FreeBSD over Linux since I have other Rpis with Linux already and wanted more experience with *BSD, jails, and ZFS. Unfortunately ZFS wasn't the best choice on an Rpi since it's more cpu intensive and switched back to UFS.

Overall it's been solid, multiple GTS updates and have it on my list to update to FreedBSD 14 but not really in a rush.

1. https://social.ecliptik.com/@micheal/statuses/01GP860MYM2CGH...

2. https://gotosocial.org/

3. https://github.com/cloudflare/cloudflared

# Install apt dependencies !apt install dotnet-sdk-7.0 git # Install Clouldflared (not on apt) !wget https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb !dpkg -i cloudflared-linux-amd64.deb # Download StableSwarmUI !git clone https://github.com/Stability-AI/StableSwarmUI # Download ComfyUI backend %cd /content/StableSwarmUI !mkdir /content/StableSwarmUI/dlbackend %cd /content/StableSwarmUI/dlbackend !git clone https://github.com/comfyanonymous/ComfyUI %cd /content/StableSwarmUI/dlbackend/ComfyUI # Setup ComfyUI !pip install -r requirements.txt

curl -L --output cloudflared.deb https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb && sudo dpkg -i cloudflared.deb && sudo systemctl restart cloudflared

Something like cloudflared would be awesome. https://github.com/cloudflare/cloudflared

if you're on windows, you can install it with the exe: https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-windows-amd64.exe (or https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-windows-386.exe if your using 32bit windows.)

So, the "more than one" issue is kind of discussed HERE and HERE but for sure, for whatever reason, this caused me sleepless nights.

%cd /content/naifu !pip install virtualenv && bash ./setup.sh !curl -Ls https://github.com/ekzhang/bore/releases/download/v0.4.0/bore-v0.4.0-x86_64-unknown-linux-musl.tar.gz | tar zx -C /usr/bin !curl -Lo /usr/bin/cloudflared https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64 && chmod +x /usr/bin/cloudflared !/content/naifu/venv/bin/python -m pip install -qq pytorch_lightning==1.7.7

Anyway, here is the Github link for Cloudflared (aka Cloudflare Tunnel client) which should allow you to remotely tunnel into your Synology server instead of using the HTTP-based reverse proxying method: https://github.com/cloudflare/cloudflared

As an alternative to traditional ingress, you can use cloudflared to expose web apps on Cloudflare via encrypted tunnels: https://github.com/cloudflare/cloudflared