edit:
I needed to edit ~/.config/qui/config.toml and bind the host to “0.0.0.0”

I’m running Debian (12) and I just installed qui, a single binary dropped in /usr/local/bin. When I fire it up, I can access the web interface on the local machine via localhost:7476, but I cannot access it over the LAN via the server’s IP. Firefox just says ‘Unable to connect’.
I can access a dozen other services over the LAN, and as far as I’m aware there’s no firewall enabled by default.
What gives?

  • undefined@lemmy.hogru.chEnglish
    8·
    13 hours ago

    Be careful if there’s a public IP address. I think some operating systems even include IPv6 with 0.0.0.0 so that if there’s a public one assigned this might open it up to the world.

    • lemmyvore@feddit.nlEnglish
      0·
      2 hours ago

      Yeah it’s a very good rule of thumb to always bind to explicit IPs.

      Another issue with 0.0.0.0 is that it will bind to basically everything, including whatever bridge or tunnel interfaces you may have up on that machine. And that’s how you end up with random services exposed through VPNs and God knows what, when you thought it was a “private” service that only lives on your LAN.