[solved] Why can't I access this service over the LAN?
from AMillionMonkeys@lemmy.world to selfhosted@lemmy.world on 16 Aug 21:16
https://lemmy.world/post/50750139

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?

#selfhosted

threaded - newest

scott@lem.free.as on 16 Aug 21:21 next collapse

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

s38b35M5@lemmy.world on 16 Aug 21:21 next collapse

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.

luthis@lemmy.nz on 16 Aug 21:28 collapse

‘Its always DNS’ should be on a shirt. Last problem I had was DNS.

s38b35M5@lemmy.world on 16 Aug 21:32 collapse
anamethatisnt@sopuli.xyz on 16 Aug 21:21 next collapse

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

undefined@lemmy.hogru.ch on 16 Aug 22:56 collapse

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.

[deleted] on 16 Aug 21:35 next collapse

.

irmadlad@lemmy.world on 16 Aug 21:56 collapse

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