pewpew VS cloudflare-ddns

OUr house web server has a home page with useful links, and in particular to a simple wiki on the same box. Without any pushing (that never works) the rest of the house has slowly learnt to use it, so the calendar, the wish lists, the pet histories, holiday ideas, all sorts of stuff are on it. The server also hosts simple apps like JS clocks, calculators and of course the [0] pewpew attack map (maybe a little less funny these days, but hey).

[0] https://github.com/hrbrmstr/pewpew

https://github.com/hrbrmstr/pewpew and https://github.com/qeeqbox/raven might be places to start.

Full list: https://github.com/hrbrmstr/pewpew

In fact, it's been so stereotypical for so long that more attacks come from China that this fake 'network attack dashboard' has a 'china mode' to make it look like more attacks are coming from China https://github.com/hrbrmstr/pewpew. It's almost a decade old.

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