In a few minutes you will connect to a server with plain ssh, using a certificate instead of a copied key. You need a Nokku workspace and a Linux server where you have sudo.
Open your workspace
Deploy the core first, then open the sign-in link that nokku recover prints. You land signed in.
Add a passkey on your profile so you never wait for a link again.
Install nk on your laptop
curl -fsSL https://get.nokku.sh/nk | shWindows and the other options are in Connect to servers.
Sign in with nk
nk --api https://nokku.example.com loginUse the address you open your workspace at. Your browser opens and shows a short code. Confirm it matches the one in your terminal.
Add a server
In the web app, open Servers and enroll a server. The web app shows the commands to run on the server, with your address filled in. They look like this:
curl -fsSL https://get.nokku.sh/nokkud | sudo sh
sudo nokkud --api https://nokku.example.com enroll # paste the token when asked
sudo systemctl restart nokkudThe server shows up in your workspace. Depending on the token, you may need to approve it in the web app first.
Give yourself access
In the web app, open the server and grant yourself a Linux account on it, for example ubuntu.
Connect
nk ls # the servers you can reach
ssh ubuntu@my-server # use the name nk ls showsThat’s it. nk fetched a certificate in the background, and the server checked it.
No firewall change is needed. Opening port 4022 only makes connections a bit faster, see Network.
Something not working?
Run nk doctor. It tells you what to fix. Troubleshooting covers the common cases.
Next steps
- Bring your team in: Invite people and Grant access.
- Understand what just happened: What happens when you type ssh.
- Servers where you can’t install the daemon: Servers without the daemon.