Hello,
I have some problem with the ACLI
I followed the installation and and create an API key and all as expected. After the authnetcation, I am getting error on Activation id for cloudId null not found error
acli confluence auth status
✓ Authenticated
Site: xxx.atlassian.net
Email: my email
Authentication Type: api_token
acli confluence blog list
✗ Activation id for cloudId null not found.
✗ Error: command execution failed
acli --version
acli version 1.3.14-stable
Seems there is no work around for me to get that working, Jira stuff works, but why this confluce doesn’t work?
Thanks FixAndre for your update.
Yes I am belongs to a enterprise plan, and the URL
https://your-site.atlassian.net/wiki defininlty working in the browser
My Account has access to the Confluce and I am one of the Spaces Owner, I keep editing updating wiki every day.
Yes I do have most recent version of ACLI, it’s actually just downloaded today
cli version 1.3.13-stable
I tried multiple version, on windows on macbook, and I tried api token, Oauth from web
Seems Jira works well but only wiki/confluce cli doesn’t work.
I’m also hitting this issue with cli version 1.3.14-stable.
I also have access to my site and it’s definitely working in a browser. The Oauth from web only request Jira scope which seems odd to me.
API token auth approach gives errors about missing CloudID despite the confluence config file having the CloudID set.
I face the same issues as mentioned above. Oauth from web, only gives me permissions for Jira not for Confluence.
API Token gives me:
acli confluence auth status
✓ Authenticated
But then I face errors:
acli confluence space list
✗ Activation id for cloudId null not found.
✗ Error: command execution failed
acli confluence space view
✗ Error: required flag(s) “id” not set
On macOS 26.3 (25D125)
acli version (available via homebrew):
❯ acli --version
acli version 1.3.13-stable
You’re using an outdated version 1.3.13-stable. Update to the latest version 1.3.14-stable.
Follow this link:
❯ brew tap atlassian/homebrew-acli
brew install acli
✔︎ JSON API cask.jws.json Downloaded 15.4MB/ 15.4MB
✔︎ JSON API formula.jws.json Downloaded 31.9MB/ 31.9MB
Warning: atlassian/acli/acli 1.3.13-stable is already installed and up-to-date.
To reinstall 1.3.13-stable, run:
Please advice.
same issue on acli version 1.3.14-stable
✗ Activation id for cloudId null not found.
✗ Error: command execution failed
this only fails for acli confluence, acli jira commands work just fine.
also tried this via web:
acli confluence auth logout, followed by acli confluence auth login --web, however the web consent screen doesn’t show any Confluence scopes as an option, suggesting that the token the CLI uses is valid for Jira only?
I am getting the same thing on linux
acli version 1.3.14-stable
hope they can fix this soon
I am facing same issue. This is a critical bug and blocking from actual usage of this feature.
I can report the same issue. I am authenticated with an API token (because Web login auth doesn’t work since it contains the same OAuth scopes as for Jira)
> acli --version
acli version 1.3.14-stable
> acli confluence auth status
✓ Authenticated
> acli confluence page view --id 1234567890 --body-format storage
✗ Activation id for cloudId null not found.
✗ Error: command execution failed
Is this a vibe coded application?
Hitting this same issue on 1.3.14-stable on MacOS.
I am also receiving Activation id for cloudId null not found.
when trying to run acli confluence page view --id 1400428448
That is the right command to access https://{my org}.atlassian.net/wiki/spaces/dev/pages/1400428448/{page title} right?
Same issue.
Confluence Cloud Standard
MacOS 26.3
I’ve installed multiple versions from homebrew with the same result: 1.3.9, 1.3.11, 1.3.14, 1.3.15
We have multiple developers trying to use it with the same results.
I upgraded to acli version 1.3.15-stable, the issue with cloudId persists.
Same issue here as well with 1.3.15-stable
Hello,
Thanks for raising this issue and for your patience while we investigated.
The underlying problem causing the
Activation id for cloudId null not found.
error when running Confluence commands (e.g. acli confluence blog list) has now been identified and fixed in the acli tool.
If you re-run your Confluence commands, they should now work as expected with your existing API token–based authentication/OAUTH based authentication. If you continue to see any issues feel free to raise it again and we will have a look.
Thanks again for reporting this and helping us improve the tool.
just to confirm - would that fix be part of 1.3.17-stable?
acli confluence auth login still fails with Error: authentication failed on the web flow.