Disable @KanoczTomas btcnode on both clearnet and onion #3378
Conversation
This file contains 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
ripcurlx
approved these changes
Oct 9, 2019
There was a problem hiding this comment.
utACK - We'll re-add @KanoczTomas nodes as soon as they are stable again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In PR #3263 we temporarily disabled @KanoczTomas btcnode's onion host, as it was having issues and it seems that @KanoczTomas is unavailable to maintain his btcnode. Unfortunately now it is generating monitoring system alerts on both clearnet and onion. This PR disables both clearnet and onion hosts, until @KanoczTomas returns and fixes his node. Hope he is okay.