docs(deploy): add nginx TLS reverse-proxy example#98
Open
acooks wants to merge 1 commit into
Open
Conversation
Add a ready-to-edit nginx config that terminates TLS and reverse-proxies to jt-server, including the websocket Upgrade handling, plus a "Running behind an HTTPS reverse proxy" section in the deployment guide. Pairs with the wss:// client fix so JitterTrap can be served over HTTPS. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
deploy/jittertrap-nginx.conf.example— TLS termination + websocket-awareproxy_passtojt-server.deploy/README.md(expands the existing one-line mention).Why
jt-serverserves the HTML5 client and the websocket on one HTTP port. Exposing it over HTTPS needs a proxy that terminates TLS and forwards the websocketUpgrade/Connectionheaders — easy to get wrong (omit them and the live-data feed silently fails to connect). This gives users a working template.Pairs with #96 (the client now selects
wss://automatically on HTTPS pages).Testing
This is the exact config used on a live deployment (nginx + certbot in front of
jt-server): the page loads over HTTPS and the websocket upgrade completes (101 Switching Protocolsoverwss://).🤖 Generated with Claude Code