The configured Atlassian site could not be found with the provided credentials.

[MRK]

I logged into my rovo dev accounting using a new api key (lost the already created one) and I am getting this error message. 

╭──────────────────────────────────────────────────────────────────────────────╮
│ WARNING: The configured Atlassian site could not be found with the provided │
│ credentials. │
╰──────────────────────────────────────────────────────────────────────────────╯

╭─ You are not authorized to perform this action ──────────────────────────────╮
│ │
│ Please check your API key and email address are correct. │
│ │
╰──────────────────────────────────────────────────────────────────────────────╯

It was working fine till a few hours ago. And I use the email and api key to authenticated and I am successfully logged in, yet I see the api key/email address error. Please advice.

[Dr Valeri Colon _Connect Centric_]

@S Mohan Ramkumar This usually happens when Rovo Dev accepts your new API token but hasn’t finished linking it to your site. Even though login works, the CLI can’t find a site where Rovo Dev is enabled. Re-log in with the same email that owns the site, confirm Rovo Dev CLI is enabled, and give the new token a few minutes to propagate. If you have multiple accounts, make sure you’re using the right one—this error often clears on its own.

[Jorge Cammarota]

You can validate the API key outside of Rovo to ensure it's working:

`curl -D- \
-u your_email@company.com:YOUR_API_TOKEN \
-X GET \
-H "Accept: application/json" \
https://companyname.atlassian.net/rest/api/3/project`

If the return is 200 OK → the key is valid. If it's 401 or 403 → permission problem or invalid key.