this post was submitted on 23 Nov 2025
76 points (97.5% liked)

Selfhosted

53128 readers
948 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
 

LOL Not really, but boy it has been a day. Started at 7:00 am and I finally resolved (?) the issue. In fact I've got through every last bit of my network, and at this point in the evening, I actually don't have a solid reason why the issue was present. Something in my VPN settings glitched, or something got triggered on pFsense and got hung up....something, something with Tailscale. It wasn't CLoudflare this time. LOL

You ever do so much to a problem that when you 'fix' it, you have no real idea what the fix truly was? You ever have a problem and find all the shit you cobbled together in the name of 'just get it running and back online'? I did, and decided that I would fix that shit too. It took all flippin' day.

You guys that do this for a living....I salute you! jebus crispies!

ETA: 8 bells and all's well today.

you are viewing a single comment's thread
view the rest of the comments
[–] SnotFlickerman@lemmy.blahaj.zone 13 points 20 hours ago* (last edited 20 hours ago) (1 children)

When you do it for work, you log what you have changed each time you make a change to try to fix it, and you log what you revert, so you can keep track of what you have tried, what worked, and what didn't and have a clearer idea of what the solution was.

Sometimes it really does take a while to nail down though, and sometimes it isn't entirely clear why what worked worked. Especially if you're a junior network engineer without as much experience.

[–] tburkhol@lemmy.world 2 points 13 hours ago

I made a self-hosted forgejo repository of /etc. Commit messages aren't always informative, and I've never actually gone back to the repository to figure something out, but it's there, just in case. Me cosplaying a sysadmin.