this post was submitted on 23 Oct 2025
541 points (99.5% liked)

Selfhosted

52474 readers
1409 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] mhzawadi@lemmy.horwood.cloud 108 points 1 day ago (1 children)

can confirm, its always DNS. Even when it looks like a network issue, its DNS

[–] aarRJaay@lemmy.world 25 points 1 day ago (1 children)
[–] ramble81@lemmy.zip 22 points 22 hours ago (3 children)

Oh man. One of my old companies, the Devs would always blame the network. Even after we spent a year upgrading and removing all SPOFs. They’d blame the network…..

“Your application is somehow producing 2 billion packets per second and your SQL queries are returning 5GB of data”…. “See! The network is too slow and it has problems”

[–] lka1988@lemmy.dbzer0.com 1 points 2 hours ago* (last edited 2 hours ago)

Ah, klugerblickdummkopf

[–] rumba@lemmy.zip 8 points 8 hours ago

Dev: My app's getting a 400 hitting the server. Your firewall changes broke it.

Me: You're getting to the server, it's giving you back a malformed request error. Most likely it's a problem in your client.

Dev: it worked fine until you made that change in QA.

Me: Your server is in production.

After that, I just get too busy to look at it for a while.... They figure it out eventually.

[–] fushuan@lemmy.blahaj.zone 3 points 9 hours ago

They might be referring to their brain network being to slow and having problems.