Getting a timeout error when I try accessing an fastmcp server deployed on cloud run #1781
Unanswered
Kamal-Moha
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all, I have dockerized & deployed a fastmcp server to cloud run on port 8080 exposed. When I try accessing the server in an MCP client, I get a timeout error. When I check cloud run logs, I see this “Truncated response body. Usually implies that the request timed out or the application exited before the response was finished.“
Though the dockerized fastmcp server is working fine locally when I test it. It’s weird seeing it get a timeout error in cloud run. I have used fastmcp version 2.11.2 and this is how I exposed the fastmcp
I have used the following resources in the cloud run service;
The following resources should be more than enough, I really don’t know why this is happening. Please help.
Beta Was this translation helpful? Give feedback.
All reactions