• 0 posts
  • 24 comments
Joined 8 months ago
Cake day: September 20th, 2025
  • Got a few commands to try from a terminal:

    curl https://google.com/
    curl https://<your searxng fqdn>
    

    Try from the SearXNG terminal too.

    Lastly, in the container with Apache, there should be some log directory, maybe /var/log/apache2/? Try doing a tail -f /path/to/error.log. You could also do something like docker compose logs -f and (while tailing/looking at logs), try your search again.

    If all else fails, sudo journalctl -xef and/or sudo dmesg -wT may offer something interesting.

  • Enterprise is really the only option companies like Anthropic and OpenAI have left. They’re drastically underpricing the service for what it costs to provide and users have shown that price hikes don’t fare well.

    But enterprises? Well you just made AI a core part of your software development workflow, what are you supposed to do, start manually reviewing bitbucket merge requests? Rewrite your Jenkins pipelines? No, when the price hikes come, businesses will pay, and then downsize to reduce that opex.

  • With torrents, it is generally considered to be a faux pas to not upload as well as download. Most private trackers will require that you maintain some sort of positive ratio in order to be in good standing.

    In order to upload, you need to expose ports from your download client out to the internet so that others can reach you.

    For news groups, you only download, so although your system is still able to reach the internet, your download client does not expose any ports to the internet.

    Edit: I suppose what I was trying to communicate is that with news groups, you are at less risk for being nabbed for piracy than torrents. The nature of the torrent protocol means that you are uploading (or at least making available to upload) any data that you have already downloaded. For news groups, there is no upload.

  • Maybe I ditch my plans and just establish a VLAN for IoT and guests.

    That’s a good starting point. Keep IoT away from your primary vlan (for all things holy don’t use VLAN ID 1). You can limit your outbound traffic for that vlan more easily if you want to cut your smart things off from the Internet.

    Guest WiFi/vlan can be just a straight shot to the internet, probably no need for visitors to get to your internal services.

    Eventually, you could add a DMZ where any Internet available systems like your VPN - with specific firewall rules only permitting VPN to specific locations inside your primary vlan.

  • it’s not security, just obscurity

    IIRC for my setup it’s a bit of both. My DNS API key is scoped to only handle the specific subdomain updates instead of my entire DNS account.

    I still use a wildcard for that subdomain for non-kubernetes systems, but the cert plugins for kubes is excellent at handling a LE cert per lan fqdn.

    You don’t need to register a local CA

    This was my biggest reason to move to Let’s Encrypt. I have a Hashicorp Vault instance in my homelab for secrets and I tried using it for an internal CA (like how the lab at work is set up), but trying to get on every device and add the full Vault chain to each individual system’s trust store was massive pain in the ass.

  • I do DNS challenges with let’s encrypt for either host fqnds (for my kubes cluster) or wildcard for the few other services.

    The trick is to do a subdomain off of a domain that you own (e.g. thing.lan.mydomain.com) this way, you can scope the DNS to only *.lan.mydomain.com if you’re conscious about scoped api security.

    Using let’s encrypt is nice because you can have a valid ssl chain that android, iOS, windows, and Linux all trust with their default trusts without having to do something with a custom CA (ask me how awful that process can be).

  • They mention this in the article. The difference is that since the tire sensor sends out an RF signal, direct line of sight isn’t necessary. You could throw a tracker up on a roof and grab signals from a block over.

    The missing part may be tying that signal to a specific car, but say your car gets pulled over - they could read your tires’ sensor ID and compare it to where they captured it and bam! Now you’re fucked.