FAQ and troubleshooting
Questions
- Is it a VPN?
- No. A VPN hides your browsing by sending it through someone else's server. A pen is a private place with its own sites and its own guest list. Your normal browsing keeps going straight to the internet; only pen names use the pen.
- Why not just use Tailscale?
- If you're technical and only want your own devices connected, do. Hogman is built on Tailscale's open-source pieces and runs alongside it. Hogman is for a private place for a group of people: guests join from a link, the keeper runs the guest list from a web page, every pen has its own names and certificate authority, and nothing about it shows up in public certificate logs.
- Can strangers find my pen?
- No. Pen names don't exist on the public internet, and the addresses inside the mesh aren't routable from it. The only public part is each pen's control address: it serves the join page and lets in devices that hold a valid key, nothing more.
- Can the keeper read what I send?
- No. Traffic between members is WireGuard, encrypted from one device to the other. The keeper can see who's in the pen, their devices, and which pen names get looked up. Who sees what.
- Does installing the pen's certificate let the keeper intercept my other sites?
- No. The certificate is name-constrained: it can only vouch for names ending in the pen's zone, and your browser and operating system refuse it for anything else. Leaving the pen removes it.
- Can I be in more than one pen?
- Yes. Join each with its own link. Each pen gets its own background connection and proxy, and they run at the same time.
- What does Hogman deliberately not do?
- Anything but HTTPS. No ssh, no other ports, no games or voice over UDP. Your computer joins only as a visitor: it can't be turned into a server for the pen, or into a route for the pen's traffic to your home network or the internet, and nobody in the pen can connect to it. Each of those would be one more way in for an attacker, on your computer and on everyone else's in the pen, so they don't exist and there's no setting to turn them on. Things that serve the pen are shares, each a small device of its own.
- What if I lose my laptop?
- If you still have another device in the pen, remove the lost one under Your devices straight away: its place in the pen is a file in your account, not yet locked to its hardware, so someone who copies that file can use it until it's removed. If you lost every device, your account is gone. There is no account recovery: no recovery page, no password reset and no support route, not even for pens we host, so there is nothing for an attacker to try. Ask a keeper for a new invite and start a new account; they give it back your role and kick the old one. If you run a pen, make a friend a second owner: a pen whose only owner loses every device keeps working, but nobody can manage it again.
- Phones?
- Not yet. A phone app is in the works.
- What does it cost?
- Free while we test. Raising your own pen is free forever: it's open source.
Troubleshooting
- "macOS needs you to approve the certificate on screen"
- macOS only lets a person at the Mac approve a new trusted certificate, even for an administrator. Run the join command in Terminal on the Mac itself, not over SSH.
- The browser can't find pen sites
- Only programs that use the pen's proxy reach the pen. On a Mac the
join sets your automatic proxy setting; if another tool already set one, it leaves yours
alone and prints the address to use. On Linux and Windows, set your browser's or desktop's
automatic proxy configuration URL to the
proxy.pacaddress the join printed (it'shttp://127.0.0.1:<port>/proxy.pac). For command-line tools, see joining, in practice. - "This computer cannot find the network's names yet"
- Run the same join command again. Your invite was already used to add this device, so the rerun sees the device is in, skips the invite, and goes on to check your home page. (The link won't work on another computer: ask for a device link instead.)
- Firefox on Linux shows a certificate warning
- Firefox on Linux keeps its own list of trusted certificates instead of the system's.
Download the pen's root from your home page (
/root_ca.crt) and import it in Settings → Privacy & Security → Certificates → View Certificates → Authorities. - An app says the certificate isn't trusted (Node, Python, Java)
- Some runtimes keep their own certificate list. Download the pen's root from your home page
and point them at it:
NODE_EXTRA_CA_CERTS="$HOME/pen-root.crt" node app.js # adds to Node's own list keytool -importcert -alias mypen -file "$HOME/pen-root.crt" -cacerts # Java
Python is different:SSL_CERT_FILEandREQUESTS_CA_BUNDLEreplace the whole list, so pointing them at the pen's root alone breaks public HTTPS in that program. If it also talks to public sites, make one file with both:cat "$(python3 -c 'import certifi; print(certifi.where())')" "$HOME/pen-root.crt" > "$HOME/ca-plus-pen.crt" SSL_CERT_FILE="$HOME/ca-plus-pen.crt" REQUESTS_CA_BUNDLE="$HOME/ca-plus-pen.crt" python app.py
- The join tool tried to open a browser on a server
- Add
--no-open. On a machine with no desktop there's nothing to open; the home page address is printed either way. - "is already being shared from this computer"
- That share is already running, perhaps in the background or another window. See it with
./hogman-join share list; stop it with./hogman-join share stop NAME. - A shared site says "the app isn't answering right now"
- The share is up but nothing is listening on the port you gave it. Start your app (or check the port), and reload.
- "the invite was not accepted"
- Invites work once and expire after 7 days; device links expire after an hour. Ask for a new one. If you picked a name someone already has, the tool asks for another.
- I left, and want back in
- Leaving takes your devices out, not your membership. Ask the keeper for a device link (or make one yourself from the home page on another device you still have), and join again.
Still stuck? Open an issue on GitHub with what you ran and what it printed.
Something wrong or unclear on this page? Its source is in site/docs-src; issues and fixes welcome.