nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Error: authentication failed

reloking

Hi. I was trying to set up rovodev (Windows). I installed everything, and it seems like i can use commands like ".\acli.exe --help", tho when im trying to run the "acli rovodev auth login", it is asking for my e-mail, and API token, i enter my mail n API token, but it just gives me an error - ✗ Error: authentication failed. I tried like 10 times, installed some stuff which could probably help with this, but it didnt work.

Comments

ArpitJain

I am also facing same issues on windows, tried deleting and creating api keys multiple times but the authorization fails everytime

Jovana Dunisijevic

Hi @reloking and @ArpitJain

Thank you for reaching out and sharing your experiences!

Here are some steps and checks to help resolve the authentication issue:

1. API Token Requirements

Make sure you are generating your API token from your Atlassian account at: https://id.atlassian.com/manage-profile/security/api-tokens
Important: The API token should be created without any additional scope

2. Product and Permission Checks

Rovo Dev Agents needs to be installed and enabled on your Atlassian site.
Your organisation admin needs to enable Rovo Dev CLI for your site.
You must be granted the “rovo-dev-agents-users” permission by your admin. If you are not on the access list, authentication will fail even with a valid token

3. Common Error Scenarios

If your site does not have Rovo Dev Agents or the CLI enabled, you will see an authentication error.
If you do not have the correct permissions, you will also see an authentication error.
If you are using the correct email and API token and still see “✗ Error: authentication failed,” it is likely a permissions or product enablement issue, not a problem with your token or CLI installation.

4. What to Do Next

Contact your Atlassian site admin and ask them to:
- Confirm that Rovo Dev Agents and Rovo Dev CLI are enabled for your site.
- Ensure your user account is added to the “rovo-dev-agents-users” group.
If you are the admin, you can enable Rovo Dev CLI in your site’s admin settings and add yourself to the correct group.

5. Additional Troubleshooting

Double-check that you are entering your Atlassian account email (the one associated with your API token).
Make sure you are using the latest version of the CLI.

If you continue to have issues, you can check the CLI log file for more details by running:

acli rovodev log

The log file is typically located at ~/.rovodev/rovodev.log

Let us know if this information helped!

Kindest regards,

Jovana

ArpitJain

Hi Jovana,

I have invited myself and given rovodev permissions from admin page, both on my account as well as the other account i have created api key and tested but it doesnt work

i have also tried checcking in my admin interaface andi have permission to rovodev agents.

the status stays invited despite of accepting the invitation from the email

Authentication still fails. can you help?

Jovana Dunisijevic

Hey @ArpitJain

I am so sorry to hear you're still having issues with the authentication!

The most likely reason authentication is still failing is that your user status remains "invited" even after accepting the invitation, which means your account is not yet fully active in the system.

Sometimes, after accepting an invite, the user status does not update from "invited" to "active," and as a result, authentication will continue to fail even if permissions are set correctly.

Let's try this!

Double-check that you have fully completed the invitation process (sometimes this requires logging out and back in, or accepting the invite from a different browser).
Since you're the site admin, remove your user from the Rovo Dev Agents group, re-invite yourself, and accept the invite again.
If your status still shows as "invited" after these steps, this could be a backend provisioning issue in which case we'd have to go through the Atlassian support to look into that having your email and site details so they can manually activate your account. And for that you can raise a ticket here: https://rovodevagents.atlassian.net/servicedesk/customer/portal/1/group/1/create/45

Let us know how you go!

Jov

Govard Vogard

Same problem. I paste my api-token to token.txt in .rovodev folder. And run "acli rovodev auth login --email "mail@gmail.com" --token < token.txt". Auth successful! See https://rovodevagents-beta.atlassian.net/wiki/external/Yzc2NzI4MTk3YTBhNDdiYjkzZDhhZTc3MjE0ZmE4Y2Q#Known-Issues-%26-Mitigations

ArpitJain

I tried the method you suggested, but no one responds. it's ben more than 5 days now

김종호_gjpinh

I am also facing same issues on windows, tried deleting and creating api keys multiple times but the authorization fails everytime

A2K

Is there a solution to this @Jovana Dunisijevic

I'm facing the same issue ever since upgrading to latest CLI.

I check logs as u suggested and got this:

> Failed to initialize analytics: To use Rovo Dev CLI, enable it in Rovo Dev Agents settings.

I have already enabled rovo dev cli on https://my-site.atlassian.net/dev-agents/rovo-dev-cli

And it was working before `acli version 1.2.10-stable` (i think I was on .8 version last night) but it stopped working ever since I installed that.

Did u change anything from .8 to .10 because this should've been working?

A2K

Ok, I found a fix.

I went to https://home.atlassian.com/ & then went through _View All Apps > Rovo Dev Agents CLI_ & created a new site under new subdomain of _new-site-subdomain.attlasian.net_ and it worked.

I guess it didn't like my old subdomain but API key of old one worked well I guess since I didn't create a new API Token.

김종호_gjpinh

This worked for me, thank you!

Frank Heilmann

Hello, also having problems currently unfortunately. "An unexpected error occured, exiting".

New token didn't change anything

Anybody else currently having problems?

Best regards

Jovana Dunisijevic

hey @A2K and @Frank Heilmann

Firstly, apologies for getting back to you so late! Coming back from PTO, I had to juggle a lot of things on my desk! Catching up to the community still!

Thank you for sharing your experiences and troubleshooting steps!

For the user seeing "An unexpected error occurred, exiting"—this is a generic error message that can have a few causes, especially while Rovo Dev CLI is in beta.

Let me try to help out with a few ideas:

- I'll start by suggesting to upgrade to the latest version of acli (which should be now 1.3.1-stable) but also upgrade Rovo Dev CLI which is now 0.10: https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/Rovo-Dev-CLI-v0-10-Release-Notes/ba-p/3086569

- as @A2K mentioned, creating a new site/subdomain and connecting the CLI to that can sometimes resolve authentication or setup issues—especially if your old subdomain has legacy settings or conflicts.

- Make sure you’re using a valid, unscoped API token. If you generated a new token and it didn’t help, double-check that you’re copying the entire token and not including any extra spaces.

- If you’re on Windows and using PowerShell, try running the CLI in the standard Command Prompt instead, as there are known issues with entering certain characters (like @) in PowerShell.

- If your repo is very large, try running the CLI in a smaller subdirectory to see if that helps.

Let me know how you both go!

Kindest regards,

Jovana

imtenko

This is how I solve mine getting ERROR: Authentication failed:

1.
First open PowerShell and then type this command:

```
Test-NetConnection id.atlassian.com -Port 443
```
Result:

```
WARNING: Name resolution of id.atlassian.com failed

ComputerName : id.atlassian.com
RemoteAddress :
InterfaceAlias :
SourceAddress :
PingSucceeded : False
```
2.
If this is the result after you've run the command, proceed to the next one:

Windows Steps:

Open Control Panel → Network and Internet → Network and Sharing Center

Click your connection → Properties

you can see the Connection label under the Access Type, click the name of the wifi( i assume it has color blue same as mine)
Click the properties
Select Internet Protocol Version 4 (TCP/IPv4) → Properties

Choose “Use the following DNS server addresses” and set:

Preferred: 8.8.8.8
Alternate: 1.1.1.1

7. Click OK → OK → Close.

Open you powershell again and type this:

```
ipconfig /flushdns
Test-NetConnection id.atlassian.com -Port 443

```

the result would something like this:

```

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

Test-NetConnection id.atlassian.com -Port 443

ComputerName : id.atlassian.com

RemoteAddress :

RemotePort : 443

InterfaceAlias : Wi-Fi

SourceAddress :

TcpTestSucceeded : True

```
Hope it helps

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

rovo-atlassian-intelligence