Krosoft Wiki
Auto Light Dark
Krosoft Wiki
Auto Light Dark
Breadcrumbs

Troubleshooting

Start with the section for your role. Do not include tokens or restricted page content in a support request.

For users

  • Cannot connect: check the endpoint supplied by your administrator, network access, the client connection settings and the token’s expiry. Use a token from the target Confluence instance.

  • Wrong account: ask the assistant which Confluence account it is connected as, then correct the client credentials if necessary.

  • Cannot find or open a page: check whether your account can open it in Confluence. Search may lag recent changes. An optional administrator space policy may narrow MCP access; request help through your normal access process.

  • Cannot save a change: your account needs native create or edit permission. If the assistant reports an incomplete page or a conflict, use Confluence’s editor or ask it to read the current page before revising the change.

Connection values and usage examples are in Connect your MCP client.

For developers and technical users

  • Connection rejected: use the MCP endpoint, not /info. Check the transport, authentication and protocol contract. HTTP 401 indicates authentication failure; HTTP 404 may indicate the wrong path or a disabled app. HTTP 400 can indicate an invalid protocol request.

  • HTTP 403 with an Origin header: the origin must match Confluence’s configured origin.

  • Failed tool call with HTTP 200: inspect isError and the returned error object. An HTTP success status alone does not mean the operation succeeded.

  • Invalid arguments: use this plugin’s tools/list schemas and Tools. Page IDs are positive numeric strings; reads return bodyStorage, while writes take body_storage.

  • Version conflict or truncated input: follow Safe editing and storage format. Never submit an incomplete read or blindly replay stale content.

  • Create timed out: check Confluence for the intended page before retrying; creation may already have committed.

For Confluence administrators

  • Search fails but page reads work: confirm Confluence can reach its configured base URL, that its JVM trusts the certificate, and that proxy authentication forwarding works.

  • Policy screen cannot open or save: confirm Confluence administrator permission and complete any secure-session challenge. Reload the native screen before saving.

  • Policy input rejected: list modes require 1–20 distinct valid space keys, at most 6,000 input characters. Invalid input leaves the existing policy unchanged. Use Native permissions to clear the saved filters.

  • JVM properties have no effect: a saved policy takes precedence. See Existing JVM configuration.

  • Policy unavailable or malformed: access fails closed. Repair the policy through the administration screen; investigate a storage error before retrying.

Handled responses include X-MCP-Request-ID; tool errors include requestId and errorCategory. Use the reference and request time to locate app diagnostics in atlassian-confluence.log. Authentication or routing failures before the app runs may have no MCP reference.

For a short investigation, set nl.krosoft.confluence.mcp.McpDiagnostics to DEBUG in Confluence Logging and Profiling, then restore the previous level. App events include the reference, operation, status, category and duration without usernames, credentials, queries or page content.

When asking for help

Provide the request time, app/client versions, sanitized error and request reference when available. State whether the same account can access the content directly in Confluence.

Comments, labels, history, attachments and sections

The app supports comments, labels, history, attachments and section editing under your native permissions. See Compatibility and limitations for operational limits.

An existing attachment filename requires another name or an explicit new-version upload. For files above 32 KiB, use the file-transfer tools or Confluence’s upload interface. If a section is ambiguous or stale, identify it again; use the native editor for unsupported or oversized pages. Changing a comment requires permission for that comment.

For technical users: inspect isError, errorCategory, mutationOutcome and retryGuidance. Current native access gates historical content and related records. A known validation/permission/conflict rejection is not_applied; unexpected or I/O failures are unknown. Read native state before any retry. These fields do not make creates, replies or uploads idempotent.

For administrators: attachment copies require source access and destination upload permission, with policy on both spaces. Open the administration screen in a browser and complete Confluence’s secure-session challenge. A working REST PAT alone does not sign you into that screen.

Support and security reports

Use the Krosoft Support Portal or support@krosoft.nl for support and security reports. MCPDC uses the same Krosoft support arrangement as the other products.

Support hours are Monday–Sunday, 18:00–22:00 Europe/Amsterdam (CET in winter, CEST in summer). Krosoft aims to respond within 24 hours; response varies with complexity, volume and available information. This is a response aim, not a guaranteed resolution time. See the standard Krosoft support policy. Installation/configuration, functionality, troubleshooting and upgrade/compatibility questions use this route. Product-specific support does not cover unrelated Atlassian or third-party app failures.

Provide app, Confluence, Java, UPM and client versions, request time, sanitized error and request reference. Do not include PATs, cookies, full page bodies or restricted search results. For security reports, share only the minimum diagnostic detail through the support route. Supported scope follows Compatibility and limitations; no new version, fix deadline or end-of-life extension is promised.