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.

dynamic SQL. I remember those days. I once got criticized by colleagues for “breaking” a dynamic SQL search query - you know the one - because I realized that it wasn’t building most of the query. I have no idea how it worked, but I made it put out actually valid SQL and it took forever. I forget if we rolled that back. We were using MS TFS, so probably not haha

I think it’s worth a shot. If it doesn’t work out, you can go back

You can find that in the ancient artifacts museum, right?

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.

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 ;)