Typo in sshd_config
Final
Quote expired. Nothing was held.
The quote was not paid within 15 minutes. The server was released and nothing was charged.
- Quote (done) $9.00 fixed
- Hold (skipped) not approved
- Keyboard (skipped) never lent
- Probe (skipped) not needed
- Expired · $0 not approved in time
Done · Expired · $0, not approved in time
Keyboard locked: nothing was heldthe keyboard was never lent
What this cost you
$0.00nothing held
What happened
-
Quote: $9.00, fixed before any key
A free look at the screen found: sshd will not start, or listens on the wrong port, because of its configuration. Screenshots only.
-
Expired: not approved in time
The quote was not paid within 15 minutes. The server was released. Nothing was held or charged.
PayPal, read live
Read from the PayPal sandbox at 04:28:09 UTC
No PayPal order was created. Nothing was ever held.
| Object | Status | What it means | Amount | PayPal answered | Webhook |
|---|---|---|---|---|---|
| Order | none | Never approved; Keyhold released it. Nothing was held. | — | — | — |
| Authorization | none | Never held. | — | — | — |
| Capture | none | Never charged: nothing was held. | — | — | — |
Full log 4 rows
- Quotesshd_config_error T1 $9.00
- Quotediagnosis: sshd will not start because of an error in /etc/ssh/sshd_config. Quote T1, $9.00.
- Ownerthe quote was not paid within 15 minutes
- StateQuote ready → Hold released, $0 charged: the quote was not paid within 15 minutes
Audit details full ids, PayPal-Request-Ids, invoice, quote, owner probe, ledger checks, timing
Ids
- Rescue
2884d7d3-1ca2-403d-9134-a8b097ce0a38- State
VOIDED- Invoice id
keyhold-2884d7d3-1ca2-403d-9134-a8b097ce0a38- Order
- —
- Authorization
- —
- Capture
- —
- Refund
- —
- Ending
- the quote was not paid within 15 minutes
PayPal-Request-Ids: two ticks per money call
Each call is written to the outbox with its PayPal-Request-Id before it is sent, so a retry never moves money twice. PayPal's synchronous answer is the first tick; the verified webhook is the second.
| Call | PayPal-Request-Id | API answer | Webhook |
|---|---|---|---|
| No money call yet. | |||
Ledger checks
ok captured ≤ authorized ≤ quote, one capture at most, no void after capture, refund ≤ captured.
Diagnosis and plan
sshd will not start, or listens on the wrong port, because of its configuration
- [FAILED] Failed to start ssh.service - OpenBSD Secure Shell server.
- See 'systemctl status ssh.service' for details.
1. Run 'systemctl status ssh.service' and 'journalctl -u ssh -b --no-pager | tail -n 40' to confirm whether the failure is a config syntax error or missing host keys. 2. Run 'sshd -t' to list the exact line in /etc/ssh/sshd_config that fails. 3. Back up /etc/ssh/sshd_config, then correct or revert the offending line with nano or sed. 4. Run 'sshd -t' again and make sure it prints no errors. 5. Run 'systemctl restart ssh' and confirm 'systemctl is-active ssh' reports active. 6. Check the listening port with 'ss -tlnp | grep ssh' and report the result.
Quote
- Fault class
sshd_config_error- Tier
- T1 · $9.00
- Quote hash
4f3222aadd32bbdf41227a92a662758fb823121bc082975b0d99c756e0c174ef
Owner probe, fixed at checkout
A capture happens only after this check passes twice, far enough apart, with no failure between.
- SSH login
- as
probeon port 32831, with a key only the probe holds - Probe key
SHA256:CcgWuPvbHnBojBASpsq+D15PKuJPkuBo/cq0ROAmp4M- Page
- HTTP GET / on port 32828: the page body has sha256 429d6e1517d7805977c57314076c608c7acf30e52b93b0b5103ae57152669bc8
- Spec hash
d7e283b6313789055468a76d37226f36e4a3b5037d7f9653218f6792ebc524f8
Sent as the order'scustom_id.
Timing and cost
- Created
- 2026-11-08 15:53:19 UTC
- Timing
- Judge mode, compressed timing. Capture after two passes at least 10 s apart, with no failure between. Warranty (judge mode, compressed): re-probed every 20 seconds, 6 times (2 minutes in all); the real plan is 24 hourly checks. Two failed checks in a row refund the full capture.