Hello all,
I am trying to install Jira Cloud Slack App in my workspace.
Following the guide (https://confluence.atlassian.com/jiracorecloud/jira-cloud-for-slack-950819031.html), after I Authorize the application I got an error (upstream request timeout), but the application gets installed anyway.
The resource which results in timeout is:
I can access the configuration and the bot user is created, but I don't get any direct message or in Slackbot with the next steps.
If I DM Jira bot I get
*/jira help* failed with the error "401_client_error"
Also if i invite the user to a channel. Same response to any request: connect, help, etc
Looking for possible answers I found this: https://community.atlassian.com/t5/Marketplace-Apps-questions/Slack-Integration-Jira-Cloud-instance-was-disabled-by/qaq-p/651743, but I have enabled the App.
What could be happening?
Thank you very much,
We have seen several reports of `upstream request timeout` from customers that have large enterprise grid Slack workspaces. We've been working with Slack to get to the bottom of these errors but as of yet haven't found a single solution for everyone. Best thing to do if you get an `upstream request timeout` is to contact support so we can dig in deeper.
One thing you can try meanwhile is:
The wait step can be important as sometimes the Slack platform processes the install first and then sends the uninstall which leaves the application in a strange state which also can cause 401_client_error issues.
Please let us know if you continue to have issues.
Same error for us for last 1 month, ditto problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I'm currently facing a slightly similar issue. I managed to connect Slack with Jira Cloud. But I just can't connect to a project (I'm Jira Admin)!
When I click on the connect button in slack, nothing happens.
Anyone knows how to fix that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Having same issue. Did you discover anything?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, yes!
The permission scheme associated with the project did not grant access to the "atlassian-addons-project-access" Project role (I'm not an experienced Jira admin, so rookie mistake I guess!). I gave this project role all the permissions and it worked fine :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
we have permissions in the project set with "atlassian-addons-project-access" for everything, but we are still seeing the error failed with the error "401_client_error"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here. I've installed JIRA Cloud integration. After that the integration worked for some minutes before the 401_client_error appeared.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
We are currently facing the same problem trying to connect Slack with Jira.
We've tried to reconnect the Jira app several times, but that did not help.
*/jira connect* failed with the error "401_client_error"
Is there a solution to this problem?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Beatriz, welcome to the Community!
I realize you encountered this error a few weeks ago but am wondering if you've tried again since then. The Slack connector is still getting a lot of love from our development team and the issue you saw may have cleared itself up. If you're still encountering problems, we can definitely dive in and get the right things connected again!
Cheers,
Daniel | Atlassian Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.