fix(termux-connect): Cloudflare Host header 421 - #16
Merged
Merged
Conversation
FastMCP DNS-rebinding protection only allows 127.0.0.1/localhost, so requests via *.trycloudflare.com returned 421 Invalid Host and the Grok Bot connector failed_to_load. Disable that check by default (loopback bind + Bearer still gate access); optional TERMUX_CONNECT_ALLOWED_HOSTS re-enables an explicit allowlist.
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
termux-connectfailed_to_load because/mcpreturned 421 Invalid Host through the Cloudflare quick tunnel.127.0.0.1/localhost.TERMUX_CONNECT_ALLOWED_HOSTSfor an explicit list.Test plan
git pull+ reinstall + restarttc(keep tunnel running)curltunnel/mcpwith Bearer no longer returns 421