Repository navigation
Issue <name>.pit.world certificates before the first visit (HSTS broke new names) - #30
Merged
Merged
Conversation
pit.world sends HSTS with includeSubDomains, so a browser that has seen pit.world goes straight to https://<name>.pit.world. Issuance only ran on a plain-http visit, so every name without a certificate failed its TLS handshake (alert 80) for those visitors: live.streaming.pit.world was down for desktops, and 17 of the 22 names with targets had no certificate. The server now sweeps the registry sitemap at start and every 15 minutes and asks pit-proxy-cert for every name the relay can reach and nginx cannot yet serve, through the existing weekly cap and once-an-hour guard. PIT_CERT_SWEEP=off disables it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <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.
pit.world sends
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload, so a browser that has seen pit.world goes straight to https://.pit.world. Certificates were only issued on a plain-http visit, so every name without one failed its TLS handshake (alert 80) for those visitors. live.streaming.pit.world was down for desktop users; 17 of the 22 registry names with a target had no certificate.The server now sweeps the registry sitemap at start and every 15 minutes and asks
pit-proxy-certfor every name the relay can reach (sametargetForcheck a visit makes) that nginx cannot serve yet, through the existing weekly cap and once-an-hour-per-host guard.PIT_CERT_SWEEP=offdisables it. Tests: sitemap parsing, sweep issues only for reachable names without a cert, refusals reported as missing, failing reachability skipped. 143 pass.🤖 Generated with Claude Code