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

  • 28 Posts
  • 796 Comments
Joined 8 months ago
cake
Cake day: March 24th, 2025

help-circle

  • no longer works with recent Docker, due to API versioning

    I had that issue with Portainer recently. I had to drop back to the previous docker version, and held it until Portainer works through the snag. I didn’t think about original watchtower being affected. I just got tired of having to fix broken updates, and went looking for something better. When original watchtower worked tho, it worked well.









  • Everything here is smooth sailing. I have been trying to track down a bothersome Suricata entry.

    
    202.136.163.11 PROTOCOL-ICMP destination unreachable port unreachable packet detected
    202.136.163.11 PROTOCOL-ICMP destination unreachable port unreachable packet detected
    202.136.163.11 PROTOCOL-ICMP destination unreachable port unreachable packet detected
    202.136.163.11 PROTOCOL-ICMP destination unreachable port unreachable packet detected
    

    ad nauseum. There are three individual ips. One from Singapore, one from China and one from Romania. They are being blocked, so that’s good. Thing is, these are from realitvly ‘clean’ sources:

    120.132.37.195 was not found in our database

    202.136.163.11 was found in our database! This IP was reported 5 times. Confidence of Abuse is 0%:

    On the server side, I have nothing calling out to these ip. That’s what was really bugging me. Nothing server side, just these three bothersome ip hammering Suricata. Generally, I would dismiss as benign and part of normal UDP behavior. However, it’s the constant hammering that makes me suspicious. Could be high volume port scanning. However, it could also be known attack campaigns like UDP amplification attempts.

    Other than that, I might find something to get into today.




  • Cloudflare has a ton of services from filtered/unfiltered DNS to Tunnels/ZeroTrust.

    but I set up the DNS thingy

    From this, I guessed you were attempting to use just the DNS portion like 1.1.1.1 or 1.0.0.1. If I misunderstood, me skuzi. What I’m talking about is:

    https://www.cloudflare.com/zero-trust/products/access/

    The caveat to use Cloudflare Tunnels/ZeroTrust is that you need a proper domain with which you can change the nameservers. Duckdns.org or similar won’t do. When you sign up for ZeroTrust, they will give you two nameserver entries. You take those to your domain registrar and insert those in place of the registrar’s nameservers. I got a domain name from NamesCheap for less than $5 USD.

    “I’m on my phone 100 miles away from home, open Jellyfin/Nextcloud/whatever

    Cloudflare Tunnels/ZeroTrust will do that and more. They have all kinds of bells and whistles that are available on their free tier. I didn’t need most of them. It will do all of that without having to adjust your server’s firewall like UFW. You don’t have to worry about port forwarding or such on your router. It just punches a hole in all of that, and delivers what you need. No muss, no fuss.

    To be fair, Cloudflare Tunnels/ZeroTrust is not unique. There are a plethora of ZeroTrust Tunnel providers. Ngrok comes to mind and seems to be the more popular of the alternatives, but there are others. Like I said previously, it took me a couple tries to get Cloudflare Tunnels/ZeroTrust down pat. Not so much that it was overly complicated, that’s just usually my modus operandi. I’m dense some days. LOL


  • there’s often a response like: “If you can’t configure Docker, reverse proxies, and Yaml files, you shouldn’t be self-hosting.”

    This is the part that I don’t like. Couple this with condescending labels like ‘normies’ et al, I can kind of understand why selfhosting is still something that only a small segment of the population engages in. I realize that people like to differentiate themselves from others. It doesn’t matter if you’re collecting stamps or you’re the tiddlywinks champion of the world, we like to draw a line between ‘us’ and ‘them’, which is a pretty poignant song by Pink Floyd btw.

    As @CameronDev@programming.dev pointed out, there are very serious consequences to self hosting too. The first Linux server I stood up got taken over fairly quickly, and over night began attacking other servers. That’s serious shit and the owners of said servers don’t take it lightly, and rightfully so. The owners of the platform you may be hosting on don’t take it lightly either. So, yeah, there are some basics one needs to learn and implement before they can begin a successful, resilient, hardened, server, and it’s not a lot of point and click solutions. Again…shit’s complex. It’s why there are so many specialists in the field, but now you as the selfhoster have to wear all the admin hats.

    The doors to selfhosting should swing wide for all, and I try to be as accommodating as I possibly can because I know how I struggle and have struggled with things from time to time.

    Safebox looks pretty interesting. I’ve often thought, if I were a much younger man, I would’ve loved to produce a type of ‘server in a box’. But I am well past being a younger man, so I’ll leave that up to you young guns.