Skip to content

RUNBOOK: SSH to the box is over Tailscale only; port 22 closed publicly - #63

Merged
jeffcrouse merged 1 commit into
mainfrom
runbook-tailscale-ssh
Oct 3, 2026
Merged

jeffcrouse merged 1 commit into
mainfrom
runbook-tailscale-ssh

Conversation

@jeffcrouse

Copy link
Copy Markdown
Member

Since 2026-10-02 the Lightsail instance's public firewall opens 80 and 443 only; SSH works only over the tailnet, where the instance is clapback.

Changes to packages/server/deploy/RUNBOOK.md:

  • New §6c, "SSH is over Tailscale only": the tailnet name and address (key expiry disabled), the ~/.ssh/config entry on jeffbook (HostKeyAlias clapback.seethroughlab.com, so the previously trusted host key still applies), how to put a freshly provisioned box on the tailnet before closing 22, and the two aws lightsail commands to reopen 22 for your current IP and close it again if Tailscale on the box fails.
  • §6b: the admin tunnel is now ssh -L 8000:127.0.0.1:8000 clapback.
  • §3: the key-pair download uses --profile jeff; the admin profile no longer exists (the account moved to IAM Identity Center the same day).

Verified when the port was closed: public :22 times out, https://clapback.seethroughlab.com returns 200, and ssh clapback works over Tailscale.

Docs only; no code or deploy changes.

🤖 Generated with Claude Code

Since 2026-10-02 the Lightsail firewall opens 80 and 443 only. New section 6c
records the tailnet name, the ~/.ssh/config entry, provisioning a fresh box onto
the tailnet, and how to reopen 22 temporarily if Tailscale on the box fails.
The admin tunnel in 6b now uses `ssh clapback`; section 3's key download uses
--profile jeff, since the admin profile was deleted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jeffcrouse
jeffcrouse merged commit 1675ae2 into main Oct 3, 2026
2 checks passed
@jeffcrouse
jeffcrouse deleted the runbook-tailscale-ssh branch October 3, 2026 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant