this was a fun read! I haven’t done much web UI in years, so it was nice to learn about some of the new, nice things that are available. i don’t think I’d remember some of the more advanced stuff though.

I can’t

Cloudflare tunnels - it used to be dynamic dns, but the ISP blocked ports 80/443, so I switched to tunnels.
External DNS on the Gl-Inet router, included with the product
Goodcloud, from Gl-Inet (included and really nice to have another way to get to it)

for the home self-hosting, that’s pretty much it.

For the (coming soon TM) fediverse apps in Keyboard Vagabond, add in S3, cloudflare CDN

omg i never picked up on that

I totally didn’t use Apple’s permission system to disable (not crowd strike, something similar) because it was breaking everything. In my hypothetical defense, everyone said that rollout was a disaster.

in addition to the other suggestions of checking the rame stick, do you have resource limits on your containers? It’s generally a good thing to have anyway, but I’d do that after checking the ram and cooling situation. Check your cpu temps as well.

I recently switched my home to using cloudaflare tunnels from dns because the ISP blocked traffic. my services are exposed to the Internet, so if you only want access by vpn, I’ve found tailscale to be easier than wireguard. If you want external access, you can get a domain name from CF and set up cloudflared on the host device and target the docker service names. But with both ways, you can have your ports not exposed to the Internet.

I formerly used external DNS until the ISP blocked the modem.

They’re crawling the web, the don’t need to target the fediverse specifically. The crawler will come here and it will either having programming or recognition of sites that update.

the ISP blocked my ports and cloudflare got me around it. I’ll accept the compromise ;)