Authenticate pangolin-client via a persisted login session #45
Loading…
Reference in a new issue
No description provided.
Delete branch "pangolin-client-login-config"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #44. The machine-client path verifies the websocket but the server rejects WireGuard registration without a user token (
olm/wg/register→USER_ID_NOT_FOUND), so the client role now authenticates with an interactivepangolin loginsession persisted inpangolin-client-config/(gitignored; one-timedocker run -it ... loginper host, exactly as documented for user devices).The client container also maintains its own
/etc/hostsblock for the.internalnames through a bind mount with self-cleaning markers — the DNS-host rewrite the CLI performs on a host run cannot survive inside a container, and this keeps every deploy fully in-stack with no host resolver changes.Also aligns all
pangolin-*services on the three documented Docker prerequisites (network_mode: host,NET_ADMIN,/dev/net/tun), unifies the site service key aspangolin-site, and drops the unused*_CLIENT_*env entries.Verified live on phd-razer: client connects,
.internalnames resolve host-wide, and SSH to phd-beelink and phd-tower passes passwordless through the stack.