-
Notifications
You must be signed in to change notification settings - Fork 27
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
docker installed promcord process keeps restarting #151
Comments
Can you provide more informations ? |
Sure. |
Probably related to discord-jda/JDA#1700. How often does the error occur on your system? |
Unfortunately constantly. I tried to install on 3 different linux boxes. Two with
|
Can you reproduce the issue on https://labs.play-with-docker.com/ ? |
sorry lads. Same with
I feel like I am not helping you much. The JDA issue seems a possible candidate however something is stopping you from reproducing. Are you sure this is not discord dev settings issue instead of a bug? I am completely out of my waters here. |
@dmamalis Can you send the docker-compose.yaml here ? |
It's just a copy of the sample yml. Initially I had it configured on a different port, but that is not the issue. I also tried with the original ports.
|
When i tried to do the issue, i ran |
I managed to debug this by using the Python Discord SDK to run a simple bot and check the bot settings. Turns out that this is most possibly a Bot Settings issues rather than the JDA bug. However, it only works on the If I can be of any help here, a bit more informative debugging could be useful. Also, for people who have no experience with custom discord bots, the bot settings are not quite self explanatory. Not really your fault, but it might help avoiding issues like this one. You can consider this closed as a non-issue. |
same here with docker-compose 1.29.2
|
I'm also getting this issue, any fix coming?
|
General Troubleshooting
Bug Report
promcord docker process keeps restarting. Not sure if this is a bug or a misconfiguration of the bot on our server.
The text was updated successfully, but these errors were encountered: