Commit 5de6e43
committed
docs: explain reverse-proxy geo-blocking on the browser landing page
The landing page served on GET to the MCP URL is the splash users see when
they open their connection URL in a browser. The most common "I see the
welcome page but my AI client can't connect" cause is a reverse-proxy/CDN
geo-blocking rule that drops US IP addresses, where most AI/LLM services
connect from (e.g. Anthropic's 160.79.104.0/21).
Add a section telling users that seeing this page means the URL is set up
correctly, that the block is on the proxy/CDN side rather than HA-MCP, and
pointing them at geo/country rules and their proxy access logs.
Closes homeassistant-ai#1669.1 parent 3e07aab commit 5de6e43
2 files changed
Lines changed: 18 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
993 | 993 | | |
994 | 994 | | |
995 | 995 | | |
| 996 | + | |
| 997 | + | |
| 998 | + | |
| 999 | + | |
| 1000 | + | |
| 1001 | + | |
| 1002 | + | |
| 1003 | + | |
| 1004 | + | |
| 1005 | + | |
| 1006 | + | |
| 1007 | + | |
| 1008 | + | |
| 1009 | + | |
| 1010 | + | |
996 | 1011 | | |
997 | 1012 | | |
998 | 1013 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
46 | 46 | | |
47 | 47 | | |
48 | 48 | | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
49 | 52 | | |
50 | 53 | | |
51 | 54 | | |
| |||
0 commit comments