Open
Description
📜 Description
I'm trying to connect the MCP server from the settings, I'm running on another machine and connected to my Self-Hosted instance via Tailscale network.
👟 Reproduction steps
- Take the MCP URL from Postiz
- Replace
https
withhttp
- Replace the host name with
{tailscaleIP}:5000
- Connect to the MCP (by MCP Inspector for example)
- Check the container logs
👍 Expected behavior
MCP should list the available tools
👎 Actual Behavior with Screenshots
Log error:
[0] 3|backend | MCP transport started
[1] {"level":"error","ts":1751176200.77511,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","upstream":"localhost:3000","duration":0.067429828,"request":{"remote_ip":"172.18.0.1","remote_port":"42114","client_ip":"172.18.0.1","proto":"HTTP/1.1","method":"GET","host":"TAILSACLE:5000","uri":"/mcp/MY_TOKEN/sse","headers":{"User-Agent":["node"],"Cache-Control":["no-cache"],"Accept-Encoding":["gzip, deflate"],"Sec-Fetch-Mode":["cors"],"Pragma":["no-cache"],"X-Forwarded-Proto":["http"],"X-Forwarded-Host":["TAILSCALE:5000"],"Accept-Language":["*"],"X-Forwarded-For":["172.18.0.1"],"Accept":["text/event-stream"]}},"error":"reading: context canceled"}
[0] 3|backend | MCP transport closed
💻 Operating system
Linux
🤖 Node Version
v20.18.1
📃 Provide any additional context for the Bug.
Self Hosted
👀 Have you spent some time to check if this bug has been raised before?
- I checked and didn't find similar issue
Are you willing to submit PR?
Yes I am willing to submit a PR!