this post was submitted on 16 Aug 2026
24 points (100.0% liked)

Selfhosted

61546 readers
265 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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 are viewing a single comment's thread
view the rest of the comments
[–] scott@lem.free.as 3 points 3 days ago

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