search

Androz2091 / discord-music-bot

The perfect music bot for your Discord server! 🤘
238 stars 127 forks source link

Bot Commands stuck on ... is thinking? #20

Closed Ethan1498 closed 3 years ago

Ethan1498 commented 3 years ago

Slash commands work, bring the bot into the channel, but the bot produces no audio whilst in the channel and each command has ... is thinking constantly under it

Screenshot 2021-09-14 at 14 37 35
ZhunCn commented 3 years ago

For the "is thinking?" bug, if you cloned the repository before September 8th, update to the latest commit. This was a possible issue that was fixed with #13 pull request that was recently merged. If you are using docker, you will also need to rebuild the image. I didn't encounter the audio issue, but you may want to look at #12 or #2

Ethan1498 commented 3 years ago

Hmmm, I cloned the repo today, so I am on the latest commit, the bot just won't run any command it seems, all them will get stuck on is thinking constantly until the message is deleted from the server, not sure if it could be an issue with me running it via Heroku?

ZhunCn commented 3 years ago

I do know that Heroku's free tier will cause the containers to sleep if it is inactive for more than 30 minutes, but I'm not sure if that would affect the bot's general functionality or not. Try temporarily hosting the bot on your own computer. I'm currently running the bot with Docker on unRAID OS (unix based), and it hasn't come into any issues. It has more than 1 week uptime right now.

Androz2091 commented 3 years ago

Yes, I think that FFMPEG can't run on Heroku. Same for node-opus, I'm not sure if it can be built or not, but I guess Heroku doesn't allow such heavy to install dependencies.

Ethan1498 commented 3 years ago

Okay cheers guys, I will try running the bot locally this evening and seeing if that solves the issue, if it does I will spin up an AWS instance and test that!

Ethan1498 commented 3 years ago

Okay quick update, running locally seems to have sorted this issue, so Heroku was causing the headache...

Will host on AWS instead, thank you for the help!