My org is unable to access Rovo chat

[Philip Ng]

Starting today, June 22, 2026, users in my org have started to encounter an error message stating "We're not sure what went wrong" when they try to open a Rovo chat in Confluence or Jira. This has been working for months. No changes have been made.

On one of my pages where I had rovo chat still open, I get "You don't have permission to use Rovo on this site. Please contact your Atlassian admin." when I try to send to the chat

I am the org admin. I found that Rovo is visible on the Apps list and in subscriptions but I am over my credits limit. From my understanding Atlassian is not enforcing the limits at this time so that shouldn't cause an issue. 

Also Rovo Access blocklist is empty. Rovo is not showing in user counts. Issue affects all users and all browsers. No configuration changes were made. Rovo status page shows no incident.

Any idea what might be causing this issue and how to fix it?

[Arkadiusz Wroblewski]

@Philip Ng

From my experience handling IT systems, if something happens out of nowhere, especially inside IT systems, it's pretty much most often a backend state problem.

Before opening a ticket, just take a look on Atlassian Administration under Rovo Access and IP allowlists to be sure user groups or networks didn't get accidentally blocked. If those settings look normal, it's probably a backend bug, so raise a ticket with Atlassian Support and just let them check Backend.

Best,

Arkadiusz 🤠☀️

[Philip Ng]

Rovo Access page only shows a blocklist which is empty. When I try to open a ticket for Rovo, it only gives me the option to post to the community forum

[Philip Ng]

I actually opened up a ticket with Support using my Jira Premium instead of selecting Rovo. They are reviewing the issue now

[Arkadiusz Wroblewski]

@Philip Ng

Super! 

Yeah, if I had known that I wouldn't request assistance🫢😅

But now you should wait and see what they will say.😊

[mike]

Same with the MCP server now.. Returns: "You don't have permission to connect from this IP address. Please ask your organization admin for access." 

Probably something was changed.. will raise a Ticket.

[Arkadiusz Wroblewski]

@Philip Ng 

Yep please do that.

@Philip Ng 

I requested Assistance to get attention from Atlassian.

It's hard to say without seeing logs.

Best,

Arkadiusz 🤠 

[mike]

@Arkadiusz Wroblewski 

FYI - on our end, the fix was adding https://claude.ai/** as an allowed domain in the Atlassian Rovo MCP server settings. It's something new(wasn't required before), but it solved our case.

[Arkadiusz Wroblewski]

@mike

It's not surprising

You're experiencing an active, evolving system, which is exciting but demands lots of learning and adapting all the time.