Skip to content

Error: Not actively managed by this transport #13

Closed
@TheWayneSwart

Description

@TheWayneSwart

When using http_dedicated transport on v.2.0.0 I see this error:

[2025-06-10 19:05:41] local.WARNING: Failed to save client state after updating activity. {"clientId":"e38a292c-23a0-4eb7-9d63-19aaf3b42d92"}
[2025-06-10 19:05:41] local.DEBUG: Received message {"clientId":"e38a292c-23a0-4eb7-9d63-19aaf3b42d92","frame":"{"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"Postman Client - 612b94cd-99e0-4300-ba2f-0598160f33c0","version":"1.0.0"}},"jsonrpc":"2.0","id":0}"}
[2025-06-10 19:05:41] local.WARNING: Attempted to send message to inactive or unknown client. {"clientId":"e38a292c-23a0-4eb7-9d63-19aaf3b42d92"}
[2025-06-10 19:05:41] local.ERROR: Transport failed to send response. {"clientId":"e38a292c-23a0-4eb7-9d63-19aaf3b42d92","responseId":0,"error":"Client 'e38a292c-23a0-4eb7-9d63-19aaf3b42d92' is not actively managed by this transport."}

Switching to dedicted transport, using mcp:serve everything works correctly.

But, trying to serve the MCP server using apache 2 with SSL, to no avail.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions