fix(proxy): use SNI for MITM certs, unify DB path across CLI and server#1
Merged
nnemirovsky merged 1 commit intomainfrom Apr 7, 2026
Merged
fix(proxy): use SNI for MITM certs, unify DB path across CLI and server#1nnemirovsky merged 1 commit intomainfrom
nnemirovsky merged 1 commit intomainfrom
Conversation
Two fixes: 1. MITM certificates now use the hostname from TLS SNI instead of the CONNECT target IP. tun2proxy sends IP-only CONNECT requests, causing goproxy to generate certs with IP SANs that fail Node.js hostname validation (ERR_TLS_CERT_ALTNAME_INVALID). The new sniAwareTLSConfig uses GetConfigForClient to read the SNI from the ClientHello and regenerate the cert with the correct hostname. 2. Dockerfile CMD used -db /home/sluice/.sluice/sluice.db but CLI defaulted to sluice.db (CWD). Proxy and CLI were reading different databases. Both now use data/sluice.db with a dedicated sluice-data volume for persistence across container restarts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ERR_TLS_CERT_ALTNAME_INVALIDwhen Node.js clients (OpenClaw) connect through tun2proxy.data/sluice.db) across Dockerfile CMD and CLI defaults. Addedsluice-datavolume to compose files for persistence.