-
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
problem starting for discord #55
Comments
accordingly: the user is not added to the discord server :( if you need additional data (screens or more) - I will provide it to you without any problems |
https://c2n.me/4aNTyH0 maybe this will help identify the problem |
What about logs? |
clear and /var/log/seat-8000.log is clear |
SeAT logs are stored at this directory : /var/www/seat/storage/logs/laravel-{date}.log |
[2021-02-05 07:12:48] local.ERROR: Client error: |
Ensure you have properly setup the driver, the discord app is public, the discord bot role is at top |
I checked the bot settings again. I checked the bot settings again. P.S. The problem has not disappeared :( [2021-02-05 08:30:49] local.ERROR: Client error: |
Thanks for the help. This has not been described anywhere. The error occurred because the Bot's role in the Discord server settings must be first in the list! https://clip2net.com/s/4aPHztL You may want to ask at this point in your documentation so that other users do not have these questions ... |
It is referenced in the KB, but I recently spot the readme would need some refactor anyway https://github.com/warlof/seat-discord-connector#known-issues |
after installing the module and making all the settings on the discord servers, when trying to authorize the user there is an error 500 / server error
https: //seat.хххххх/seat-connector/registration/discord/callback? code = kHKz548zL38QybiCjvKSQaCU41S5Ym & state = mknGXeRPcxhyuHGpoyeF6l6byRkPNrHV2459u30O
Please help :)
ps worked as much as possible with the configuration of this module according to the instructions.
The text was updated successfully, but these errors were encountered: