Write down how a source entry reaches an authority that speaks TLS - #34
Merged
bitcoinuniverseadmin merged 1 commit intoAug 30, 2026
Merged
Conversation
The overlay published index-doge-tap as unreachable from the day it was configured, and the hourly production smoke failed on it for a day, for two reasons this file did not warn about. The entry named http://127.0.0.1:3013 against a service that has served TLS since its certificate was issued. Every probe got an empty reply, which the overlay can only report as unreachable, and the service was running and ready the whole time. The entry now names the certificate's own SAN host over loopback, and the certificate is trusted rather than verification being switched off. The entry also carried the reader's token. The marketplace endpoints check a per-authority token instead, so every checkpoint request was a 401 while the unauthenticated readiness probe passed. A green readiness probe says nothing about the request that actually matters. Both are properties of the deployment rather than of the repository, which is why they were invisible here. The configuration table also gains the certificate file the overlay now reads. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
bitcoinuniverseadmin
deleted the
docs/overlay-reaches-doge-tap-over-tls
branch
August 30, 2026 12:01
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.
Follow-up to the two host-side corrections made while clearing the production smoke. Full diagnosis in index-doge-tap#24.
DEPLOYMENT.mddescribesUNIVERSE_EXPLORER_SOURCES_JSONbut not the two things about a source entry that are easy to get wrong, both of which had already produced an authority the overlay reported as unreachable while it was running and ready:index-doge-tapis an HTTPS listener. Its entry washttp://, so every probe got an empty reply. It now names the certificate's own SAN host, resolved to127.0.0.1through/etc/hostsso verification passes and the traffic stays onlo, with the certificate trusted throughNODE_EXTRA_CA_CERTSrather than verification being turned off.index-doge-tapauthenticates its reader API withTOKEN_EXPLORER_BEARER_TOKENand its marketplace endpoints per authority. The readiness probe passing proved nothing, because readiness is unauthenticated and the checkpoint request was returning 401.The configuration table also gains
doge-tap-ca.pem, which the overlay now reads.Documentation only. No code, no configuration in this repository.
🤖 Generated with Claude Code