Skip to content

Could not start the proxy McpError: MCP error -32001: Request timed out #8

@shaaraddalvi

Description

@shaaraddalvi

Hi, first of all, thanks for making this MCP server.

I am trying to run from latest main branch using Docker. Also, I wish to use the HTTP Streamable transport. I have built the docker image and running it with the following docker-compose service -

filesystem-mcp-workingset:
    image: cyanheads/filesystem-mcp-server:latest
    container_name: fs-mcp
    restart: unless-stopped
    environment:
      - MCP_TRANSPORT_TYPE=http
      - MCP_HTTP_HOST=0.0.0.0
      - MCP_HTTP_PORT=3010
      - MCP_AUTH_SECRET_KEY=${FS_MCP_AUTH_SECRET_KEY}
      - FS_BASE_DIRECTORY=/data
      - MCP_ALLOWED_ORIGINS=http://192.168.1.101:23010
    ports:
      - 192.168.1.101:23010:3010
    volumes:
      - /var/lib/workingset:/data

Here, I get the error after 60 seconds of starting the container -

could not start the proxy McpError: MCP error -32001: Request timed out
    at Timeout.timeoutHandler (file:///usr/local/lib/node_modules/mcp-proxy/node_modules/@modelcontextprotocol/sdk/dist/esm/shared/protocol.js:307:49)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7) {
  code: -32001,
  data: { timeout: 60000 }
}

Could you please help?

Also, is it mandatory to run the MCP server with HTTPS (behind a reverse proxy for SSL-termination)? Could I just not run it in HTTP Streamable mode without the need for HTTPS?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions