Subject: Software probe 1016653 stuck “never connected” — public key matches but registration SSH gets Permission denied (publickey)
Hi all,
I set up a new RIPE Atlas software probe (ID 1016653) on an Ubuntu box. Installation completed successfully, but the probe has never managed to connect — the portal shows it as “never connected.”
I’ve confirmed the public key in /etc/ripe-atlas/probe_key.pub matches exactly what’s registered on the portal for this probe, and I’ve re-saved the key on the portal to force a re-sync, but the issue persists.
Relevant details:
- Private key permissions: -rw------- (600), owned by ripe-atlas:ripe-atlas — confirmed correct
- No /var/atlas-probe/status/ssh_err.txt file present
- journalctl -u ripe-atlas shows repeated registration attempts, each failing quickly (not timing out) with a clean SSH rejection:
REASON_FOR_REGISTRATION NEW NO previous state files
REGHOSTS reg03.atlas.ripe.net 193.0.19.246 193.0.19.246
ssh -p 443 atlas@193.0.19.247 INIT
255 REGINIT exit with error
RESULT { “dst_name”:“Issh-permission-denied…” }
This repeats every few minutes across both reg03 and reg04, always with the same permission-denied result. Since the SSH handshake completes quickly (not a timeout/network issue) and the key is confirmed to match on both ends, this looks like the registration backend isn’t recognizing the key even though the portal shows it as saved.
Could someone from RIPE NCC take a look at probe 1016653 on the backend? Happy to provide any further logs or the exact public key fingerprint if useful.
Thanks!