Find me on Mastodon too.

  • 0 Posts
  • 21 Comments
Joined 9 months ago
cake
Cake day: January 26th, 2024

help-circle

  • We used to use Malwarebytes Corporate Edition at work.

    One afternoon all of our web servers stopped responding to traffic on port 443. I could RDC into the servers, and I could ping them, but most traffic wasn’t being passed properly.

    Despite not having made any changes, I did everything I could think of to get them to work. I tried moving them to different switches, different static IPs, Wireshark showed packets flowing, but no web traffic.

    I left the office. It was around 8 PM and I had been banging my head on my desk trying to figure out what the hell was going on.

    I came back around 10 PM, mind clear and stomach topped off. I worked a few more minutes, then heard the Outlook ding.

    Mass email from Malwarebytes CEO. Bad update. Blocked all class B IP addresses by mistake (guess which class we used). Mea culpa. So sorry. New update fixes things.

    I immediately uninstalled MWB CE and boom. Services restored.

    The next week we got our licenses refunded by our VAR and we never used that product again.


  • This got me too once. I was in the server room replacing old 110 punch panels/blocks with 8P8C connections. I lost track of cable connections, a mistake I have learned from, and I looped a patch cable into the same switch. Within moments the entire network went down.

    Forty-five minutes later and we figured out the loop.

    Another lesson learned: HP Procurve switches did not have Spanning Tree enabled by default.

    Anyway, mistakes happen, especially in IT. It’s all part of the learning experience. My boss was the coolest, chillest guy in the world so I learned and moved on.







  • No-fail kitchen garbage bag replacement.

    1. Buy high quality (not Walmart) plastic kitchen bin. Note bag size printed on giant, impossible to remove sticker.

    2. Buy proper bag size from name brand. You can spend a bit of money up front, or spend your valuable time later cleaning up garbage juice. Your call.

    3. Remove bag from roll.

    4. Open bag and scare the crap out of the dog by inflating the bag with swift, loud, jarring noises.

    5. Place bag in bin. DO NOT ATTACH YET.

    6. Starting at one corner, seal the bag around the edge while simultaneously reaching into the clean bag and forcing air out from between the bin and bag.

    7. Work your way around until entire inside of bin looks like a reverse condom.

    8. Good to go.






  • Here’s a quick method:

    Get the IP and set up the dns for the new server. Get a cert via Let’s Encrypt or self sign to get ssl working, and then start your prep.

    On the new host create the new directory structure. Note your folders, paths, and permissions. Set the permissions on the pictrs folder as 991 (sudo chown 991:991 /path/to/pictrs/folder even if that user doesn’t exist on your system. It’s for the container.

    You’ll need to edit your yml files, docker compose file, and make sure that the paths are updated, the instance name is correct, and federation is disabled (until testing is done).

    Copy pictrs and db folders from old host to new. You can skip pictrs if space is a concern, but you’ll lose your instance pics.

    Once done, copy over the containers and bring them up.

    Check for errors and diagnose as necessary.

    Once set, change the federation to on, switch your dns from old server to new, and then perform another sanity test.


  • I’m doing what you want to do now. I’m running lemmy.fan on a NAS with really good hardware on a fiber connection. My ISP provides symmetric bandwidth and doesn’t block anything, though emails can’t be sent with a local smtp server since most places don’t trust the IP addresses of residential subscribers.

    I learned a ton, I’m enjoying running things, and though it’s an open instance I don’t advertise it. I say go for it. Experiment and have fun. If it sucks and you hate it you just stop the containers.


  • Awesome question.

    The operating system, or OS, really does not care about whether it is a hard drive or a solid state drive when moving around the partitions.

    Say your hard drives are pools. One is filled with molasses, and the other has water. The partitions are like the ropes in the pool. Perhaps you have no ropes. Maybe you have three, but two are so close to the wall, and each other, that only a small amount of stuff could occupy those lanes.

    That leaves you with one really large lane. That’s your data partition.

    Water or molasses, the ropes are the same.