Closed tubbo closed 1 year ago
I haven't tried slack integration in awhile (and unaware if anyone uses it :) )
Let me try it myself tonight or tomorrow and see what happens (it could be broken)
One other thing I should point out is that this bot, just like my aggregators, has no open ports
@tubbo There is no open port, cause there is nothing to serve to an open port. All the protocols don't need open ports at the current time, they all use some form of RTTM or some protocols where its not necessary to have an open port.
@shayaantx
@tubbo There is no open port, cause there is nothing to serve to an open port. All the protocols don't need open ports at the current time, they all use some form of RTTM or some protocols where its not necessary to have an open port.
That's what I figured.
Let me try it myself tonight or tomorrow and see what happens (it could be broken)
If you need me to supply any other logs, I can definitely do that. Not sure how much help I'll be with the Java code as I'm incredibly rusty (no pun intended), but I can at least compile stuff and try it out from here.
@tubbo so your slack setup looks right, can you try with below
slack-channels=requests
Pretty sure thats why, so I added this check that prevents bot from starting if you put special chars (other than number/alpha and "-") https://github.com/shayaantx/botdarr/pull/93 (the slack.log would have the message now indicating why)
I changed my properties
file to slack-channels=requests
and that worked, thanks!
I believe I followed the documentation steps correctly, and my Docker-installed Botdarr is able to see messages in the Slack room as evidenced by its
slack.log
and these messages from the audit log:However, I don't see any response in my Slack channel:
Here's my
properties
file, sans secret tokens:(note: all of my other services are running in the same
docker-compose
env so I am addressing them by their container names)I also surmised that I had to add quotes around
slack-channels=
so that Java wouldn't think that was a comment...but that didn't seem to work either. At least withlog-level=all
I can see what's going on...setting$LOG_LEVEL
didn't really seem to work in this way.One other thing I should point out is that this bot, just like my aggregators, has no open ports. The Docker example didn't seem like it needed them, and since you're connecting to Slack over WS, I figured it's probably fine...but I'm just mentioning because I really have no idea what's going on here.
I also tried adding some scopes to the bot user but no dice: