MastodonTech.de

choan 🍉Pues <a href="https://social.anartist.org/tags/navidrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#navidrome</a> + <a href="https://social.anartist.org/tags/cloudflared" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloudflared</a> + <a href="https://social.anartist.org/tags/symfonium" class="mention hashtag" rel="nofollow noopener" target="_blank">#symfonium</a> corriendo de la mano.¿Queréis que os cuente?<a href="https://social.anartist.org/tags/despotify" class="mention hashtag" rel="nofollow noopener" target="_blank">#despotify</a>

Lou SmithI realize my home lab is a non critical learning device, but surprised to see <a href="https://mstdn.social/tags/plex" class="mention hashtag" rel="nofollow noopener" target="_blank">#plex</a>, <a href="https://mstdn.social/tags/caddy" class="mention hashtag" rel="nofollow noopener" target="_blank">#caddy</a> x 2, <a href="https://mstdn.social/tags/cloudflared" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloudflared</a>, <a href="https://mstdn.social/tags/minecraft" class="mention hashtag" rel="nofollow noopener" target="_blank">#minecraft</a> running on less than 0.22% of CPU on <a href="https://mstdn.social/tags/AMD" class="mention hashtag" rel="nofollow noopener" target="_blank">#AMD</a> Ryzen 7 5800H

Daniel KeerHere's how to setup the URL shortener <a href="https://fosstodon.org/@shlinkio" class="u-url mention" rel="nofollow noopener" target="_blank">@shlinkio</a> with Docker and a Cloudflare Tunnel<a href="https://thedxt.ca/2024/11/shlink-with-docker-and-cloudflare-tunnel/" rel="nofollow noopener" translate="no" target="_blank">https://thedxt.ca/2024/11/shlink-with-docker-and-cloudflare-tunnel/</a><a href="https://infosec.exchange/tags/Shlink" class="mention hashtag" rel="nofollow noopener" target="_blank">#Shlink</a> <a href="https://infosec.exchange/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeLab</a> <a href="https://infosec.exchange/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://infosec.exchange/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cloudflare</a> <a href="https://infosec.exchange/tags/SelfHosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosted</a> <a href="https://infosec.exchange/tags/Cloudflared" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cloudflared</a>

MikaBruh I'm still so confused about this - can any <a href="https://sakurajima.social/tags/networking" rel="nofollow noopener" target="_blank">#networking</a> people or anyone with <a href="https://sakurajima.social/tags/PiHole" rel="nofollow noopener" target="_blank">#PiHole</a>/<a href="https://sakurajima.social/tags/Pi-hole" rel="nofollow noopener" target="_blank">#Pi-hole</a> experience chime in and tell if my goal is privacy, and if I were to prioritise one, it'd be better privacy against my ISP, what should I use on my Pi-hole DNS server? - <a href="https://sakurajima.social/tags/Unbound" rel="nofollow noopener" target="_blank">#Unbound</a> as a recursive DNS server - Enable <a href="https://sakurajima.social/tags/DNS-Over-TLS" rel="nofollow noopener" target="_blank">#DNS-Over-TLS</a> (<a href="https://sakurajima.social/tags/DoT" rel="nofollow noopener" target="_blank">#DoT</a>) using Unbound and upstream DNS provider set to something like <a href="https://sakurajima.social/tags/Cloudflare" rel="nofollow noopener" target="_blank">#Cloudflare</a> - or Enable <a href="https://sakurajima.social/tags/DNS-Over-HTTPS" rel="nofollow noopener" target="_blank">#DNS-Over-HTTPS</a> (<a href="https://sakurajima.social/tags/DoH" rel="nofollow noopener" target="_blank">#DoH</a>) using <a href="https://sakurajima.social/tags/Cloudflared" rel="nofollow noopener" target="_blank">#Cloudflared</a> I initially thought you could have Pi-hole be all three but I don't think so, no?

Yehor 🇺🇦Despite some WiFi issues at the beginning, <a href="https://techhub.social/tags/Synology" class="mention hashtag" rel="nofollow noopener" target="_blank">#Synology</a> RT6600ax is the best home <a href="https://techhub.social/tags/router" class="mention hashtag" rel="nofollow noopener" target="_blank">#router</a> I ever had. It's like <a href="https://techhub.social/tags/Asus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Asus</a> but with modern UI and some additional features for <a href="https://techhub.social/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeLab</a>.I finally have a separate <a href="https://techhub.social/tags/VLAN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VLAN</a> for my public services and potentially misconfigured Linux containers.I also replaced <a href="https://techhub.social/tags/Traefik" class="mention hashtag" rel="nofollow noopener" target="_blank">#Traefik</a> with the <a href="https://techhub.social/tags/cloudflare" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloudflare</a> tunnel and I like it.Oh, and I fixed my broken <a href="https://techhub.social/tags/AdGuardHome" class="mention hashtag" rel="nofollow noopener" target="_blank">#AdGuardHome</a>. Its only upstream was a DoH, but DoHs were not allowed on a router to make traffic monitoring more precise.How's your weekend?<a href="https://techhub.social/tags/HomeServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeServer</a> <a href="https://techhub.social/tags/cloudflared" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloudflared</a> <a href="https://techhub.social/tags/CloudflareTunnels" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudflareTunnels</a> <a href="https://techhub.social/tags/SynologyRouter" class="mention hashtag" rel="nofollow noopener" target="_blank">#SynologyRouter</a> <a href="https://techhub.social/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a> <a href="https://techhub.social/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a> <a href="https://techhub.social/tags/adguard" class="mention hashtag" rel="nofollow noopener" target="_blank">#adguard</a> <a href="https://techhub.social/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a> <a href="https://techhub.social/tags/doh" class="mention hashtag" rel="nofollow noopener" target="_blank">#doh</a>

lj·rk @WHY2025Thinking about my (still WIP) <a href="https://todon.eu/tags/PiHole" class="mention hashtag" rel="nofollow noopener" target="_blank">#PiHole</a> setup. AFAICT, the guide for <a href="https://todon.eu/tags/DoH" class="mention hashtag" rel="nofollow noopener" target="_blank">#DoH</a> with <a href="https://todon.eu/tags/cloudflared" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloudflared</a> at <a href="https://docs.pi-hole.net/guides/dns/cloudflared/" rel="nofollow noopener" target="_blank">https://docs.pi-hole.net/guides/dns/cloudflared/</a> only coveres using DoH between the PiHole and the upstream DNS provider (e.g., Cloudflare, Google, etc.). But if I want to use DoH between my browser and my PiHole, I seem to need another DoH Proxy, which makes request flow like this:1. incoming on dns.ljrk.org:443 (traefik reverse proxy) 2. forwarded to 127.0.0.1:80 (DoH Proxy #1) 3. upstream classic DNS resolver on 127.0.0.1:53 (PiHole) 4. forwards any non-blocked requests to 127.0.0.1:5053 (DoH Proxy #2) 5. upstream DoH DNS resolver such as 1.1.1.1:443/dns-requestOf course, most PiHole setups are local and I'll probably end up opening dns.ljrk.org only through a <a href="https://todon.eu/tags/TailScale" class="mention hashtag" rel="nofollow noopener" target="_blank">#TailScale</a>/#HeadScale <a href="https://todon.eu/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a>, but my browser may still prefer to speak DoH instead of RFC1035. I'm also not sure how <a href="https://todon.eu/tags/DNSSEC" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNSSEC</a> plays into this...

ＣｏｎｅｊｏAhora con el proyecto iniciado de <a href="https://mstdn.mx/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a>, tengo una duda para los que son expertos y saben mucho más que yo:Aunque lo único que haría público sería un sitio web/blog, en teoría al haber un túnel con <a href="https://mstdn.mx/tags/cloudflared" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloudflared</a> ya toda la infraestructura está (más o menos) expuesta al internet. ¿Será suficientemente seguro, o mejor me pongo a estudiar el uso de <a href="https://mstdn.mx/tags/NginxProxyManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#NginxProxyManager</a> como segunda capa?

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#cloudflared