33
[solved] Why can't I access this service over the LAN? (lemmy.world)
submitted 1 month ago* (last edited 1 month ago) by to c/selfhosted@lemmy.world
9 comments fedilink hide all child comments
 

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?

all 10 comments

sorted by: hot top controversial new old
[–] 12 points 1 month ago (2 children)

Check if you need a flag when starting it to bind 0.0.0.0 instead of 127.0.0.1

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 9 points 1 month ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 1 month 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.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 7 points 1 month ago (3 children)

    Its always DNS.

    But seriously, I'm not familiar with qui, but there could be a whitelist approach to access by default. Maybe it's blocking access until you whitelist or configure it to accept all.

    Its not likely your local firewall is an issue since you can access other services, but the fact that you don't know means you should find out. I think Debian uses ufw by default, but I think Debian ships with it disabled.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
    • [–] 7 points 1 month ago

    Because the process might only be listening on the loopback address (127.0.0.1/localhost).

  • permalink
  • fedilink
  • source
    •
    [–] 2 points 1 month ago

    Solving problems in less than 30 minutes, LOL Nice job.

  • permalink
  • fedilink
  • source
    •
    [+] 1 point 1 month ago
    [deleted]
  • permalink
  • fedilink
  • source
    •