bot cannot respond from container about master-bot HOT 9 CLOSED

Howdy @LilJohnDee,
Gonna go ahead close this issue, if you have any other issues or suggestion, please feel free to post them.

Much Love
-Bacon

from master-bot.

Howdy my friend,

it is not a bother, happy to help.
even with the docker compose method of running the bot, there should still be a Master-Bot/logs folder created,

highly likely to see something similar to the message below for the last few log entries

01-19-2023 11:58:43 error: Client Listener TRPCClientError: Guild not found
01-19-2023 11:58:43 error: Client Listener TRPCClientError: Guild not found

Guild not found can happen when the bot containers were build/created with the bot still in the discord server,
kick the bot from the discord server, then start the docker container, then re-invite the bot to the discord server, should be good to go.

I hope this helps, if you have a different error in the log file, post it here, and we can work on getting ya running

Much Love
-Bacon

from master-bot.

sorry it took so long... i accidentally wrecked the VM i had it running on and had to rebuild the environment after rescuing my files but that was exactly it!! Thank you so very much!! i have tested a couple of times now and it is exactly as you stated, error and all :)

I am going to try to push/pull the composite container over to my unraid server but i figured i would ask: Can the composite container now be moved to another location without having to drag the accompanying containers along with it?

ps: apologies for marking the issue as a bug, i know it was 100% operator error but i thought i had to choose a tag >.<

from master-bot.

No worries,
That's a good question, I'm not sure.
I personally haven't used unraid or tried to move a composite container.

Let me know how it goes, I'm curious.
Best of luck my friend

Much Love
-Bacon

from master-bot.

after a bit of reading and testing, it seems i will need to mess with the Dockerfile to have all 4 images built within the same container.... if i manage to figure it out would you like me to post the file here?

feel free to close this issue as the bot is operational as intended :) Thanks again for the help!!!

from master-bot.

my apologise my friend for the delayed response, more than welcome to post a PR for review.

Master-Bot/Dockerfile has a couple of lines for standalone use.

i do believe it is possible to run the docker compose on unraid through the gui,
or third possible option is to create a container for docker compose to run it.

Some more info can be found on the docker compose pr #742

I hope this helps

Much Love
-Bacon

from master-bot.

hopefully this wont reopen the issue.... but i was just wondering if there is any documentation on the dashboard?

• click "dashboard" at localhost:3000
• redirected to loaclhost:3000/api/auth/signin
• click "sign in with Discord"
• redirected to 0.0.0.0:3000/api/auth/signin?csrf=true
• click "sign in with Discord" again
• redirected to https://discord.com/oauth2/authorize?client_id=MYCLIENTID&scope=identify%20guilds%20email%20applications.commands.permissions.update&response_type=code&redirect_uri=http%3A%2F%2F0.0.0.0%3A3000%2Fapi%2Fauth%2Fcallback%2Fdiscord&state=YD-MJq1YvkCu1oibRasQK9b54CA-CbYHAIjKbrtfw3o
• click authorize
• redirected back to the sign in at 0.0.0.0:3000/api/auth/signin?error=OAuthCreateAccount with "try signing in with a different account" banner about the button
  

i feel like i am missing something somewhere but im not seeing anything obvious to me :(

Thanks again for all your help; and of course the amazing bot!!

from master-bot.

Howdy, there is a small section Here on redirects

Go to the OAuth2 tab in the developer portal, copy the Client ID to DISCORD_CLIENT_ID and generate a secret to place in DISCORD_CLIENT_SECRET. Also, set the following URLs under 'Redirects':

• http://localhost:3000/api/auth/callback/discord

• http://domain:3000/api/auth/callback/discord
  Make sure to change 'domain' in http://domain:3000/api/auth/callback/discord to your domain or public ip.

double check that you have the redirect urls in your Discord Dev Portal to the example above, in most cases http://localhost:3000/api/auth/callback/discord should work (private bot use)

If you want to use a public IP address or a domain, make sure the port is open (public bot use)

I hope this helps.
If you are still having issues, open a new issue, and we'll try to get ya running

Much Love
-Bacon

from master-bot.

Thanks, i have seen this bit and messed around with it a bit and think im getting closer.... but will play with it some more and open a ticket if i cant figure it out :) Thanks again for all your help!

from master-bot.