Never a dull day in this #selfhosting journey: editing important #DNS records while your child is on summer holiday - and may come see you every few minutes - is a very interesting exercise in concentration.
Special thanks to nonna (grandma) for helping with childcare this morning
I'm hoping I'm successful in setting up a more solid #CDN for my personal website because I keep DDOS'ing myself (from a simple Mastodon reply to a federated Wordpress post - 8k followers will do that).
Wish me luck!
P.S.: another moment of gratitude / deep appreciation for #VarnishCache which has been providing rock solid caching to my #Ghost site. Now I need to take care of my #Wordpress site with a pro CDN solution (Varnish isn't an option sadly bc of the Wordpress setup / I don't have direct access to the server)
Someone mentioned using #BunnyNet as a CDN on here (I wish I remembered to get a referral code from them... they shoulda gotten some credit).
I moved my only serious web site to it. What's interesting to look at is how much visibility I got over traffic, and then how it gave me the ability to fight off the bots. There's a story in this graph.
On the 11th I switched over. You can see this huge spike in green 4XX traffic. Some bot out of Singapore hammered the site overnight. I got up and turned on bot detection, but it was in detect only mode. So you can see the yellow line at the bottom (5XX errors) and the green line still quite high. These bots trigger a lot of errors (possibly intentionally).
There's a mysterious 2-hour window yesterday where it seems I did no traffic at all. I don't think it was -that- bad, but I was definitely messing with stuff.
Finally I put the bot detection into "challenge" mode. The 5XXs have basically stopped, and the 4XXs represent (I think) failed challenges, plus the inevitable bots looking for wp-login.php and various attack probes. So far, I'm quite happy with it. I've pretty much moved all my websites to it, though everything else adds up to basically nothing.
I also added the overall traffic graph to show the normal traffic for comparison. And I included some graphs of the VM's performance over roughly the same time period.
And of course, if you want to give it a go, here's my referral link. (I'm gonna have to figure out who I saw mention it and just paypal them some cash or something)
#Development #Previews
Kelp · A customizable UI library that needs no build step https://ilo.im/164ypi
_____
#Library #HTML #CSS #WebComponents #CDN #WebStandards #WebDev #Frontend
"Creating my own small CDN for my Mastodon instance metalhead.club"
https://thomas-leister.de/en/creating-own-small-cdn-for-mastodon-instance-metalheadclub/
I've created my own little CDN for my Mastodon instance metalhead.club recently! And it works well! Here's how I did that
Phoenix.new – The Remote AI Runtime for Phoenix
https://fly.io/blog/phoenix-new-the-remote-ai-runtime/
#ycombinator #fly #fly_io #elixir #docker #cdn #hosting #servers #networking #deploy_app_servers #close_to_users #postgresql_clusters #heroku_competitor #heroku_alternative
Während ich mir die Performancergebnisse zu meinem metalhead.club CDN angesehen habe, ist mir aufgefallen, dass die Namensauflösung einen beträchtlichen Teil der Ladezeit für internationale User ausgemacht hat.
Woran lag's? An CNAMES!
Wieso CNAMES problematisch sein können, erfahrt ihr in diesem zweiten Blogpost, den ich während meiner Arbeiten am CDN geschrieben habe:
"Globale DNS-Auflösung durch Verzicht auf CNAMES beschleunigen" -
https://thomas-leister.de/globale-dns-aufloesung-beschleunigen-cname/
Seit einigen Tagen werden Medien meiner Mastodon-Instanz metalhead.club global verteilt über ein eigenes CDN ausgeliefert.
Das verringert die Latenzen für Benutzer aus nicht-EU Ländern und sorgt für weniger Frust bei den Ladezeiten.
Was ein CDN ist, welche Implementierungsmethoden es gibt und wie ich mein kleines CDN umgesetzt habe, erfahrt ihr in meinem neuen Blogpost:
"Ein eigenes kleines CDN für meine Mastodon-Instanz metalhead.club" - https://thomas-leister.de/mastodon-media-storage-cdn/
I keep seeing governments treat DNS resolvers like censorship tools. Obviously, they’re not meant to be.
Blocking at the DNS level is imprecise and doesn’t remove bad actors. It’s like trying to fix a leaky faucet with a sledgehammer.
Now they're going even further, pressuring CDNs like cloudflare to block access to piracy or malicious content. But here's the catch: CDNs serve thousands of sites from shared infrastructure. One misfire, and you can literally break half the web.
Just looking at what happened in Spain with La Liga is a perfect example of how not to fight piracy. To block access to illegal streams of soccer matches, La Liga pushed for CDN-level blocking.
Instead of just stopping shady streams, the blocks affected entire domains. Legit websites went offline. Entire CDNs were caught in the crossfire, news outlets, small businesses, hobby sites. All because they happened to sit on the same servers/ips as of flagged URLs.
For instance, none of them are discussing reducing ticket fees, so normal people can take their family to a stadium, or even streaming subscription costs. It's a shame.