Skip to main content
Use this path when the service already answers on a public HTTP(S) URL. kombify.me terminates TLS and proxies the browser to that origin. Private, loopback, and link-local targets are rejected on this path. In everyday terms: your app already has a web address that anyone on the internet can open. kombify.me gives it a second, tidier name on kombify.me, with HTTPS handled for you. Visitors type the kombify.me name and kombify.me passes them through to your app. Not sure this is the right kind? Read Public, private or redirect first.

​
Before you start

  • The origin must be reachable from the internet over HTTP or HTTPS.
  • A signed-in kombify account registers names through api.kombify.io. Self-hosted installs register with an API key after email verification.
  • Connected StackKits and Techstack flows can register first-party kit names for you.

​
Give the service a name

  1. Register a base name for the homelab. Hosted accounts get {homelab}-{you}.kombify.me. Self-hosted installs get sh-{homelab}-{device}.kombify.me.
  2. Register the service under that base. First-party kit slugs such as auth, id, and coolify always become {base}-{service}.kombify.me.
  3. Point the service at the public origin URL.
  4. Expose the service route. Unexposed service names stay unpublished.
Then open https://{base}-{service}.kombify.me in a browser. For a plain-language walk-through with example names, see Get your first kombify.me address.

​
What to expect after each step

  • After registering the base name, kombify.me answers with the full base name. Write it down; every app name is built from it.
  • After registering the service and its origin, the name exists but is still switched off. Visitors get a “not exposed” answer (404) until you expose it.
  • After you expose the service, the name accepts visitors. Changes can take up to about a minute to show, because kombify.me keeps a short routing cache.
  • On a self-hosted install, while the e-mail address is not verified yet, new names start paused and visitors get an “inactive” answer (503). Finish the verification, or set the address to active.
Anyone who knows the name can open a public address unless the app asks for a login. Keep apps with sensitive data behind their own login. Reserved apex names such as auth.kombify.me stay unused. Kit login still lands on {your-lab}-auth.kombify.me.

​
If the origin is not public

Stop here and follow Reach a private service. Do not publish a localhost or LAN-only URL on the public proxy. Local-only names stay on the homelab resolver that StackKits installs. They are not kombify.me names.

​
If something goes wrong

More checks: kombify.me troubleshooting. To pause, change or remove an address later, see Change, pause or remove an address.