Watching away from home needs two things: the firewall rule (the installer made it) and a port forward on your router (you have to do this one).
Steps
- Give the server machine a fixed local address, with a DHCP reservation on your router or a static address.
- In your router's admin page, forward external TCP 5466 to that machine's port 5466.
- Sign the server in to your kinode.tv account if you haven't.
- Wait up to five minutes for the next heartbeat, or restart the server to send one now.
Your server can't see its own public address from behind a router, so the hub fills it in from where the heartbeat came from.
Test it properly
Test from a phone on mobile data, not wifi. A phone on your own wifi will succeed for the wrong reason.
HTTPS is automatic
Servers connected to the hub get real HTTPS on the same port, with a trusted certificate that renews itself. Nothing else needs opening. If your router has DNS rebind protection, local connections fall back to plain HTTP inside your own network while remote ones stay encrypted. Allow-listing s.kinode.tv in the router's rebind settings brings the padlock back at home.
When it doesn't work
- No port forward, or it points at an old local address after a reboot. Use a DHCP reservation.
- Carrier grade NAT. Some providers and most mobile broadband don't give you a real public address, so port forwarding can't work. Ask your provider for a public address, or use a tunnel.
- Double NAT. A router behind another router needs the forward on both.
- Windows thinks your network is public. The firewall rules only apply to private networks. Settings, Network, set it to Private.
Have your own domain or reverse proxy? Put the full address in Settings, Maintenance, Public address and it takes priority.
Ask below if you get stuck, and please don't post your public IP.