IPTunnel Documentation
Back Home
Overview

FAQ

Common questions about install codes, DNS, service operation, and reinstalls.

The code expired before I could use it

Install codes expire in 5 minutes from generation. Generate a new code from /slowdns and run the installer immediately after copying the code. If you are on a slow connection, have the terminal and the panel open side by side before you generate.

The code says "already used" but the install failed

The installer automatically calls the release endpoint on failure, which restores the code if the install token was not yet used. If you see "already used," it means either:

  • A previous run on the same machine did activate and confirm successfully (check /opt/slowdns/config/license.json).
  • The install token expired (10 minutes) before the release call completed — the code cannot be restored in that case. Generate a new one.

Can I reinstall on the same server?

Yes. Generate a new install code, then rerun the same install command. The installer is idempotent — existing SSH accounts and the SQLite database are preserved. Binaries, service files, and config are overwritten.

Can I use one code for multiple servers?

No. Each install code is single-use. Generate a separate code for each server you install on.

Install finished but I never saw "Activation confirmed"

This means the confirm step was skipped (the installer exited before calling the confirm endpoint). Common causes:

  • A service failed to start — check systemctl status slowdns-api slowdns-dnstt --no-pager.
  • The install token expired (10-minute window exceeded — usually only on very slow VPS builds). Reinstall with a new code.

The file /opt/slowdns/config/license.json will be missing or absent if confirmation did not complete.

Client connects to dnstt but gets no tunnel

The most common cause is a DNS misconfiguration. Check in this order:

  1. dig +short A ns1.example.com — must return the VPS IPv4.
  2. dig +short NS slowdns.example.com — must return ns1.example.com.
  3. systemctl is-active slowdns-dnstt — must return active.
  4. Check that the client is configured with the delegated tunnel domain (slowdns.example.com), not the public host (ns1.example.com).