Skip to main content
Use this path when the service is not reachable from the internet. kombify.me does not fetch the private address itself. A Techstack node agent on the homelab opens an authenticated connection and forwards bounded HTTP(S) requests. In everyday terms: your app only works inside your home network, for example at an address like 192.168.x.x. You do not have to open anything on your router. A small helper at home, the Techstack node agent, connects out to kombify.me and carries visitors’ requests in. Not sure this is the right kind? Read Public, private or redirect first.

​
Before you start

  • A Techstack node agent must be running on the homelab that can reach the origin.
  • The route must use the private-target type, not the public proxy.
  • Service exposure still defaults off. Enable it only when you want the public name to accept traffic.

​
Open the private name

  1. Register the service name the same way as a public address.
  2. Set the target as a private HTTP(S) origin on the homelab.
  3. Keep the Techstack node agent connected.
  4. Expose the service route.
  5. Open https://{base}-{service}.kombify.me.
If the agent is disconnected, the public name stays unavailable and asks the client to retry. Reconnecting the same owner restores forwarding. Another owner’s agent cannot serve the route.

​
What to expect after each step

  • After registering the name and setting the private target, the name exists but is switched off. Visitors get a “not exposed” answer (404).
  • After the node agent connects, the route can carry traffic. If the agent is not connected yet, visitors get a “try again in a few seconds” answer (503).
  • After you expose the route, https://{base}-{service}.kombify.me opens your app.

​
Limits to know about

  • Pages and files are limited to 10 MiB per request or response, and each request has 30 seconds.
  • Live streams and arbitrary network connections are not supported. The relay carries web (HTTP and HTTPS) requests only.

​
If something goes wrong

More checks: kombify.me troubleshooting. To use this with a StackKits server, see Use an address with a StackKits server.

​
Keep local names local

LAN-only browsing stays on the resolver that StackKits installs on the homelab. kombify.me does not publish *.lan.kombify.me names.