• 0 Posts
  • 17 Comments
Joined 2 months ago
cake
Cake day: March 16th, 2025

help-circle



  • Right, I didn’t have any issues running it on a pi for years too. The problems came when I started messing with things. So, really my advice is to help save people from ideas like mine.

    I decided one day to take a bunch of old laptops and create a proxmox cluster out of them. It worked great, but I didn’t have a use for them, I was just playing. So, I decided to retire the pi and put the pihole on the cluster. HA for the win!

    I did that and came woke up a few days later to my family complaining that they had no internet. I found the pihole container on a different node and it wouldn’t start. Turns out with proxmox you need separate storage for HA to work. I had assumed that it would be similar to jboss clustering which I’m familiar with, and the container would be on all the nodes and only one actice at a time, with some syncing between nodes. Nope.

    What’s worse is the container refused to move back to the origional node AND wouldn’t start. The pi was stored away at this point so I figured it would be easier to just create a new container, but duh, no internet. Turn off dns settings on the router, bam have internet.

    Eventually set up the old pi again, and it took me a while to figure out what I had done wrong with proxmox. But while I was figuring it out it was nice to have the backup.

    Now I always have two running on different hardware, just in case.









  • Might need more info about your setup. The reverse proxy probably has some logs you aren’t looking at. Most bots from what I’ve seen do ip:port scans hitting every ip and every port. Nginx reverse proxy manager or something similar isn’t going to forward ip:8123 to home assistant. A straight router port forward will, but the reverse proxy manager will look at the domain GET request for https://ha.hit_the_rails.net to your LAN ip:port. It’s a little security through obscurity as they have to know your sub+domain.

    For a time I had port 22 open and forwarded directly to a server. Constant bot traffic. Changed the port, put an ssh honeypot on 22, and it almost completely went away. Sure the bots could be smart enough to scan and find another open ssh port, but they rarely did. I assume because anyone savvy enough to change the ssh port is savvy enough to not allow default logins like ubnt:ubnt and root:1234 which were by far the most common logins I got in the honeypot.


  • yaroto98@lemmy.orgtoLinux@lemmy.mlLinux PC build (2025)
    link
    fedilink
    English
    arrow-up
    1
    ·
    24 days ago

    Ahhhh have you double checked to make sure your GPU will fit in your case? I see you went micro atx for case and mobo, but gpus nowadays be chonky. It should fit, but I’ve seen new builds where the gpu didn’t fit in a normal atx case due to layout and mobo positioning.


  • yaroto98@lemmy.orgtoLinux@lemmy.mlLinux PC build (2025)
    link
    fedilink
    English
    arrow-up
    3
    ·
    25 days ago

    I have a similar build, but everything is a generation behind. I really like Garuda Linux. Arch keeps the latest drivers comin’ and It’s a nice easy install. Btrfs+snappertools come setup by default, and it’s saved my bacon a few times. Really nice to be able to have grub boot to a snapshot and just work. And the snapshots are auto created everytime pacman is run.



  • yaroto98@lemmy.orgtoAsklemmy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    54
    arrow-down
    4
    ·
    1 month ago

    Think of it like a protest. Most protests don’t DO anything, but he forced the entire senate to sit and listen to him for 25 hrs rant about how bad things have gotten. I’m sure there was work and stuff they were supposed to vote on that he effectively delayed. But that’s all it really was, a record breaking protest.