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?
You must log in or # to comment.
Check if you need a flag when starting it to bind 0.0.0.0 instead of 127.0.0.1
Be careful if there’s a public IP address. I think some operating systems even include IPv6 with
0.0.0.0so that if there’s a public one assigned this might open it up to the world.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.
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
ufwby default, but I think Debian ships with it disabled.‘Its always DNS’ should be on a shirt. Last problem I had was DNS.
Because the process might only be listening on the loopback address (127.0.0.1/localhost).
Solving problems in less than 30 minutes, LOL Nice job.
deleted by creator
