Troubleshooting¶

Known issues and limitations¶

Missing attachment file ID on Server¶

For some Confluence Server versions / configurations, the attachment file ID is not returned by the API (#39).

In that case, {attachment_file_id} automatically falls back to the content id, so the default export.attachment_path template still produces unique filenames out of the box.

If you prefer human-readable filenames over numeric IDs, set export.attachment_path to use {attachment_title}{attachment_extension}, e.g.:

cme config set export.attachment_path='{space_name}/attachments/{attachment_title}{attachment_extension}'

Self-signed or internal CA certificates¶

Self-hosted instances often use certificates issued by an internal CA. Point connection_config.ca_bundle at a PEM file with that CA instead of disabling connection_config.verify_ssl.

Attachments fail with scoped API tokens¶

Some Confluence Cloud sites return attachment download links (/download/attachments/...) that scoped API tokens are not allowed to use (401 Unauthorized; scope does not match). cme then retries the download through the REST API endpoint. If attachments still fail, check that the token has the read:attachment:confluence scope.

Connection issues behind proxy or VPN¶

There might be connection issues if your Confluence Server is behind a proxy or VPN (#38). If you experience issues, help to fix this is appreciated.

Reporting bugs¶

Open an issue on the GitHub issue tracker and include:

Your Confluence flavour and version (Cloud, Server, Data Center)
The exact command you ran
The full output, ideally with cme config set export.log_level=DEBUG enabled
A minimal example page (if possible) reproducing the issue