Choose what your Linux machine does.
One guided menu for your home IP updater, Connect services and browser terminal. Run the command below as your ordinary Linux user. Setup explains each change before you approve it.
1. Open a terminal on your Linux machine
Paste this command. It downloads the menu over HTTPS and checks the application package before running it.
curl -q --proto '=https' --tlsv1.2 -fsS https://honkip.com/install.sh | sh
If Ubuntu's personal-folder permissions need a small repair, setup explains it and asks before continuing. Your existing files stay in place.
Run without sudo. A root shell must switch to the ordinary user you want HonkIP to run as.
2. Install and sign in
Choose Install HonkIP, then Sign in to HonkIP. Until sign-in succeeds, only Sign in and Exit are shown. Leave this terminal open while you open honkip.com in your browser, enter the code and approve your request. Pressing Ctrl+C cancels sign-in. Once approved, the full services and settings menu appears automatically. Your HonkIP password stays on the website.
3. Pick your features
- Home IP updater — every plan. Keeps your home name pointing at this internet connection. It does not open ports.
- Connect — eligible plan. Reach selected web apps, TCP or UDP services without router port forwarding, including behind CGNAT. Choose a preset or your own local port. Saving starts the connector automatically. If background running is available, you can return to the menu; otherwise keep the terminal open while it runs.
- Browser terminal — separate Pro add-on, not available right now. Open this Linux user’s terminal through HonkIP. No public SSH port is needed. On Ubuntu or Debian with systemd, setup can offer to install a missing local-only SSH service. Choose Yes and approve sudo to continue; existing SSH installations stay unchanged.
Sign in on honkip.com in your browser, enter the code shown by your own installer, and check the request before approving. The console never asks for your HonkIP password.
HTTPS websites and SSH are different
HonkIP automatically provides HTTPS and a public certificate for your website address. For the local connection, choose what your app already uses: HTTP for a local app without a certificate, or HTTPS when it has one. Local HTTPS certificate checks stay on. SSH is a separate encrypted terminal service, not an HTTPS website.
4. Start and check
Saving a service starts its connector. Choose My connections for status, testing, starting and stopping. This menu stays open until you choose Back. Choose Choose one service → Stop this service to stop only that connection and keep its settings. Choose the same service again to start it. Stop all connections and IP updater stops this machine’s updater and all Connect services.
Choose Settings and help → Keep running to stay available after sign-out and restart; setup asks before Linux requests sudo approval. If background mode is unavailable, keep the running terminal open.
Browser-terminal access is managed separately: choose SSH terminal → Stop terminal access to stop it.
Keep HonkIP up to date
The installed menu checks for a newer Linux app in the background. Choose Settings and help → Check / install app updates to check now and approve an update. Your sign-in and saved services stay in place. After updating, exit and reopen the menu, then choose My connections → Start connections.
The browser-terminal agent has a separate update option under SSH terminal. Update and reopen the Linux menu first, then choose this terminal update. It keeps the server’s existing approval, keys and settings. Older terminal installations automatically get a new private Python environment prepared before the switch; you do not need to remove or reconnect the server. Active terminal sessions close during an update; stopped terminal access stays stopped. Downloads use HTTPS and checksum verification. Installation always asks first.
Linux requirements
Python 3.10 or newer, virtual environments and a supported dependency wheel for your Python/CPU combination. Setup detects Debian/Ubuntu, Fedora/RHEL, Arch, openSUSE and Alpine package families and shows guidance. We test on Ubuntu 24.04. Other distributions are not tested yet and may need extra steps.
Older distribution packages may need a newer Python. If Python or its virtual-environment support is missing on Ubuntu/Debian, setup shows the exact proposed package step. You choose whether to refresh package lists, and separately whether to open the package installer. Nothing is installed without your approval; setup never adds software repositories. Other distributions receive package guidance to review with their administrator. The optional local SSH step also asks before installing system packages. Setup does not change the firewall or grant sudo. The optional Keep running step asks for sudo approval to keep enabled background services available after sign-out and server restart. Open browser-terminal sessions end on reboot; open a new session afterwards.
Package SHA-256: 51974bf603027791d3c4def736184ed0cdc9b0a4d4ba8ea4a7f8dec2a35728c9