Connection & discovery

Fixes for a client that can't find or reach the host. A Windows host on a Public network is under Windows firewall.

Finding the hostCopy Anchor Link

Another streaming host (Sunshine, Apollo, …) is installedCopy Anchor Link

Sunshine and its forks (Apollo, Vibeshine, …) want the same ports, TCP 47990 even with GameStream off. You see address already in use in the host log, pairing that fails, or the wrong host answering.

Run punktfunk-host detect-conflicts, or read Competing streaming server on the console's Troubleshooting page. Then uninstall the other host, or keep both by moving Punktfunk's port: Switching from Sunshine.

The host isn't found on the networkCopy Anchor Link

Discovery uses mDNS on the local network, and anything that blocks it hides the host. Check:

• The host is running: systemctl --user status punktfunk-host (Linux), punktfunk-host service status (Windows, elevated).
• Android: tap Allow… under Local network access is off at the top of the host list.
• Both devices are on the same subnet. mDNS doesn't cross routers or most VPNs; add the host by its IP address instead.
• The host firewall lets discovery in: Ports → Enable the profiles.
• Local discovery is on under Host (an advanced setting).

The host is asleep and won't wakeCopy Anchor Link

A client wakes only a host it has seen awake, and only if the host's network card is armed for it. A Linux host logs Wake-on-LAN is NOT armed with the command for its card. Arming for every host: Wake-on-LAN → Arming the machine.

Pairing is rejected / the client can't connectCopy Anchor Link

The host admits only paired devices. Approve the device in the web console, or pair with a PIN: Pairing. A host that lost its identity (config deleted, OS reinstalled) needs pairing again.

Over a VPN other than Tailscale or NetBird, the host can count the device as coming from the internet: there is no Approve, and a PIN from Pair a device fails with "Pairing isn't started on the host". Click Arm PIN on the device's row under Waiting for approval, and set its access yourself: the default is for a friend.

After connectingCopy Anchor Link

A plugin's interface doesn't loadCopy Anchor Link

Plugin pages come from their own port, TCP 47993, next to the console's 47992.

• Trust this plugin's port once: your browser hasn't accepted the host's certificate for that port. Press Open in a new tab, accept the warning, and come back.

• The panel stays empty: a firewall rule saved before 47993 existed blocks it. Refresh it:

  Copy Text

  sudo ufw app update punktfunk-web && sudo ufw reload    # ufw
  sudo firewall-cmd --reload                               # firewalld

  On Windows, run the setup again; it adds both console rules.

• Plugin interfaces are unavailable: the console couldn't open that port. Set another with PUNKTFUNK_UI_PLUGIN_PORT in host.env and restart the console.