-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slack bot integration Error: not_allowed_token_type #123
Comments
@ImagineerNL ill run thru steps 2moro night or next night and see if i can reproduce |
@ImagineerNL I ran through https://github.com/shayaantx/botdarr/wiki/Install-Slack-Bot and didn't have an issue (well I was running an older jdk 8 and got certificate errors, but once I upgraded it was fine) I did update slack api #124, but I couldn't reproduce your error Did you create a classic app? or a modern one? (looks like eventually classic apps are gonna die, so guess these instructions will need to change) If you're on discord or matrix or slack, post your handle, and I can look at your issue live too |
I'll dig a bit further in what it might be, thanks for looking. |
classic Slack apps are no longer supported, any chance there will be support for modern apps? getting the same not_allowed_token_type error. |
Would it be possible to push this to live (and to the docker version)?
Modern App, as Classic apps cannot be created anymore. |
@ImagineerNL @ACupOfAvgJoe I will spend some time this week going through that PR and see what I can do to get it working again |
I spent some time tonight updating the PR to get off RTM mode and onto socket mode for slack modern apps, see 6392b19 I've also made a new wiki page for creating modern slack apps to work with the bot in general here https://github.com/shayaantx/botdarr/wiki/(wip)-Install-Slack-Bot-via-Slack-modern-app Both are still wip I will work on it more tomorrow night. |
Thank you. The only error still in the log is from lidarr, which i dont use and i have removed the docker variables |
That warning occurs when you don't have lidarr configured (you can ignore it if you don't use lidarr) Yea it def won't work without changes, hopefully I can get bulk of it working tonight |
i didnt assume that one had anything to do with this item; just noted it as an fyi, as that is the only one that comes up as 'unconfigured', while all other integrations that arent configured dont show up in the log either. And no rush; take your time. |
@ImagineerNL I pushed the fixes for latest version 5.6.16, the wiki is updated with all required scopes I tested most functionality of the bot via slack and it all seems to work, lemme know if you find any issues, otherwise I'll close the issue |
Updated the docker, Followed the updated wiki, no new errors. And at least now i get a message in log, so i know the slack socket connection is open And a timeout message popped up in slack 'Error - Request failed with status code=404, reason=Not Found' which was resolved by setting SONARR_V4 to true. I'm guessing it's an error with the scopes, and for now i'll need to dig in to it a bit more to see what i'm missing. It seems no action on your part is needed yet. |
lemme know if you want to debug it live on slack or discord I noticed if you add scopes to the modern app, I had to reinstall the app to the workspace each time (as I was testing) |
@ImagineerNL any issues ? |
Trying to install this as a slack bot.
Created the app, added the oauth permissions as per instruction.
Copy/pasted the SLACK_BOT_TOKEN from the slack app settings "Bot User OAuth Token" , but get this error in my logs and it won't connect to slack.
I'm using the docker app from the Unraid appdir, and manually added the needed variables from the readme.
Total log seems error free besides a lidarr warning (i dont have lidarr):
The text was updated successfully, but these errors were encountered: