Desktop client can't connect to self-hosted instances with DNS that resolves to private IPs

(#3619) Bug Closed: Fixed desktop self-hosting

Reproduction steps

  1. Set up a self-hosted instance.
  2. Set up your DNS such that it resolves to a private IP address (this is a relatively common use case for routers that don't support hairpin NAT).
  3. Try to connect to it using Fluxer Canary with support for self-hosted instances.
  4. See the issue above.
Note: As soon as the DNS resolves to a public IP, if your router supports hairpin NAT, you can restart Fluxer Canary and connect.

Observed behaviour

Tried to connect to my self-hosted instance with Fluxer Canary, and almost immediately see "Couldn't connect to [hostname]. Try again." Expected to be able to log in.

Platform

macOS, Self-hosting

  1. computron changed the status from Awaiting confirmation to Fixed

2 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote
Status changed from Needs triage to Awaiting confirmation
Fixed in desktop canary 2026.1008.12411. An instance you pick yourself can now resolve to a private address, including split-horizon DNS that returns a LAN IPv4 address next to a public IPv6 one. A public instance still can't send the app into your local network.