Incessant tinkerer since the 70’s. Staunch privacy advocate. SelfHoster. Musician of mediocre talent. https://soundcloud.com/hood-poet-608190196

  • 3 Posts
  • 19 Comments
Joined 2 months ago
cake
Cake day: March 24th, 2025

help-circle





  • Many people even intentionally turn off sleep-mode in “green” drives so that they don’t shut down automatically.

    I’ve always sort of wrestled with this conundrum. Powering on and off HDDs exerts the most wear imho, and so is it better to keep them powered on in order minimize intermittent start/stop wear, or power them off and assume that keeping them powered on means constant wear?







  • I have a question about xcaddy, if anyone would be so kind as to school me. I too would like to geoblock with Caddy. I have investigated the process and of course it uses xcaddy. Having no knowledge of xcaddy, how does that work? Is xcaddy for building modules for Caddy? Does it run separately or in conjunction with Caddy? Does it interfere with Caddy in any way. My hesitation stems from the embarrassingly long time it took for me to wrap my noodle around how Caddy works. IKR? Now it seems so simple, but I’d like very much not to mess up my Caddy installation fat fingering my way through xcaddy. Yes, I know screw ups build knowledge bases, but I’m really trying to be careful and not go in like a bull in a china closet.

    'presh


  • I’ll probably get boo’d but NetData covers just about everything I could want to monitor, and then some. If you don’t want to hook up to the mother ship, you can use the /v3 switch in the url on your homarr dash, or equal like:

    https://netdata.mycoolserver.duckdns.org/v3

    Also, as has been mentioned, ntopng is pretty awesome as well.






  • As you probably know the crowdsec bouncer doesn’t directly parse logs or do checks like F2B filters. It queries the crowdsec LAPI for decisions and applies them. The “allowed” or “whitelisted” IP logic is handled at the Security Engine or LAPI level, not by the bouncer itself.

    You can whitelist an ip in /etc/crowdsec/whitelists.yaml or even whitelist decisions in the whitelist.yaml as such:

    name: private-ips
    description: Whitelist local and private IPs
    whitelist:
      reason: "Allow local and private IPs"
      ip:
        - "127.0.0.1"
        - "192.168.1.0/24"
      cidr:
        - "10.0.0.0/8"
    

    Then issue sudo systemctl reload crowdsec. Kind of the same concept as F2B’s ignoreip option. If you are using Tailscale to administer the server, then it’s easier to whitelist. IIRC, you can use cscli decisions add --type whitelist --ip 192.168.1.100 --duration 1y but it doesn’t add them to the whitelist.yaml. Instead it keeps them in crowdsec’s database managed by LAPI. To undo: cscli decisions delete --ip 192.168.1.100 --type whitelist

    https://docs.crowdsec.net/u/getting_started/post_installation/whitelists/