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.

  • Gobo@lemmy.worldEnglish
    1·
    18 days ago

    Sometimes the fix has been done but the effect takes a while. For a cache to age out or a change to propogate. It all depends on what you are working with/on. Or you made a change but forgot to restart a specific service.

    Meanwhile even though you did a fix correctly and aren’t aware of it, since it doesn’t seem to work you change something else and break it again inadvertently.

  • dotslashme@infosec.pubEnglish
    1·
    18 days ago

    Man, I know that feeling. One thing that helped me better deal with issues like this, was to have a changelog. Basically I write down what a setting was, what I changed it to and a reason. If something goes wrong, I can at least undo what changes I’ve made and see if it helps. It’s not perfect, but it might shave some hours off a RCA.

    • youmaynotknow@lemmy.zipEnglish
      1·
      18 days ago

      This is what led me to set up SnipeIT and keep a log on every change on each device. It gets wild as the devices and services increase.

      • irmadlad@lemmy.worldOPEnglish
        1·
        18 days ago

        SnipeIT

        I’ve seen the app rolling around in Awesome Lists, but always thought it was for larger operations with a lot of infrastructure and not necessarily a home lab. I might look into it seriously.

  • Snot Flickerman@lemmy.blahaj.zoneEnglish
    0·
    18 days ago

    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.