Tutorials

Install the Agent

Install the Kepeink agent on Linux, macOS, or Windows with a one-line installer and connect it to a tunnel using your agent token.

Install the Agent

The agent is the small program that runs on your machine, dials out to Kepeink, and holds your tunnel open. This page covers installing it and connecting it to a tunnel with your agent token.

Before you start

  1. Sign up and open the dashboard.
  2. Create a tunnel and choose its backend mode (proxy or static) and target.
  3. Copy the agent token the dashboard shows for that tunnel — it looks like kpt_.... The token identifies the tunnel, so keep it secret.

Install as a background service (Linux and macOS)

Run the one-line installer. It downloads the agent, installs it as a system service, and starts it. Paste your token inline so it connects right away:

curl -fsSL https://cdn.kepeink.hu/install.sh | sudo sh -s -- --token=kpt_xxxxxxxx

Without a token, the installer runs and then prompts you for one:

curl -fsSL https://cdn.kepeink.hu/install.sh | sudo sh

The service is named kepeink-agent, starts on boot, and reconnects on its own if the connection drops.

Install on Windows

Run this in an elevated PowerShell session. It downloads and runs the installer with your token:

Invoke-WebRequest -UseBasicParsing https://cdn.kepeink.hu/install.ps1 -OutFile $env:TEMP\kepeink-install.ps1; & $env:TEMP\kepeink-install.ps1 -Token kpt_xxxxxxxx

Run in the foreground instead

If you would rather not install a service — for a quick test or a one-off demo — use the run bootstrap. It downloads the agent into the current directory as ./kepeink and runs it in the foreground with human-readable logs:

curl -fsSL https://cdn.kepeink.hu/run.sh | sh -s -- --token=kpt_xxxxxxxx

Stop it with Ctrl-C. Nothing is left installed.

Confirm it is working

Once the agent is running, open your tunnel's assigned hostname from the dashboard in a browser. You should see your local service served over HTTPS. If the page does not load, check that:

  • the local target you configured is actually listening, and
  • the agent process is running and shows a connected session in its logs.

Next steps

Get started