docs: leonard adds status update on SSH/Clone and iMessage pause
This commit is contained in:
@@ -25,4 +25,31 @@
|
||||
|
||||
Grok can read the board via MCP `read_file`. Leonard handles the commit relay until Grok's Gitea write token path is resolved.
|
||||
|
||||
**Next move:** Fire up the chess tutor on port 3050.
|
||||
**Next move:** Fire up the chess tutor on port 3050.
|
||||
|
||||
---
|
||||
|
||||
## 🟢 Leonard's Updates
|
||||
|
||||
### 2026-06-20 — SSH Config + Clone URL Status
|
||||
|
||||
**Gitea clone situation:**
|
||||
- HTTP on port 3000 is confirmed reachable from the internet (VPS tests pass), but the user's ISP/carrier appears to block outbound port 3000 — even from a mobile hotspot
|
||||
- SSH on port 22 is open but **not wired to Gitea** — the `AuthorizedKeysCommand` isn't configured in `sshd_config`, so SSH keys added through Gitea aren't recognized
|
||||
- The user's public key (`ssh-ed25519 ... tonyjbala@gmail.com`) was added to my (Leonard's) Gitea account, but that doesn't help without sshd config
|
||||
|
||||
**Next step:** Request sudo access to add this to `/etc/ssh/sshd_config`:
|
||||
```
|
||||
AuthorizedKeysCommand /opt/gitea/gitea serv --config /opt/gitea/custom/conf/app.ini
|
||||
AuthorizedKeysCommandUser gitea
|
||||
```
|
||||
Then restart sshd. Once done, the user can clone via SSH:
|
||||
```
|
||||
git clone ssh://gitea@74.208.111.99:22/Tony_tech/chess-project.git
|
||||
```
|
||||
|
||||
**iMessage/Photon update (on hold):**
|
||||
- Device token reissued (valid through June 27)
|
||||
- Project secret rotated
|
||||
- Sidecar running but **outbound blocked** — free plan doesn't allow sending to the user's number
|
||||
- Paused per user request
|
||||
Reference in New Issue
Block a user