Error after Installation and the first boot about master-bot HOT 10 CLOSED

I'm not sure if this info is helpful,
Sidenote - $ in the url will trigger both these errors, BUT ${whatever}, ${}, or \$ in the url will not trigger any errors at build
, oddly if there is a $ in the DATABASE_URL will still give these errors for the NEXT_PUBLIC_INVITE_URL, despite the $ being in the DB URL string

This Information was very helpful. The links were alright, but the password contained a $. After removing it, it worked like it should. Thank you very much once again Bacon!

from master-bot.

I'm not sure if this info is helpful,
Sidenote - $ in the url will trigger both these errors, BUT ${whatever}, ${}, or \$ in the url will not trigger any errors at build
, oddly if there is a $ in the DATABASE_URL will still give these errors for the NEXT_PUBLIC_INVITE_URL, despite the $ being in the DB URL string

This Information was very helpful. The links were alright, but the password contained a $. After removing it, it worked like it should. Thank you very much once again Bacon!

Awesome, enjoy!
@Bacon-Fixation great stuff!

from master-bot.

Howdy, was able to replicate this error message

Make sure the .env is in the root folder, and run npm run dev in root folder.

I get this error when I try to start the dashboard and bot separately with .env in the wrong folder

noticed the first command in log is not "npm run copy-env && concurrently "npm run dev:dashboard" "npm run dev:bot" in log, strongly indicates npm run dev was not ran in root folder

I hope this helps

Much Love
-Bacon

from master-bot.

been trying to match the Errors more exact,
i was able to get both sets of errors to appear when there is a $ in the NEXT_PUBLIC_INVITE_URL url string.

Example
NEXT_PUBLIC_INVITE_URL="https://discord.com/api/oauth2/authorize?client_id=yourclientid&permissions=8&scope=bot$"
https://pastebin.com/TJwnD9qm (Replicated Error with .env in proper place and followed README as presented)

I'm not sure if this info is helpful,
Sidenote - $ in the url will trigger both these errors, BUT ${whatever}, ${}, or \$ in the url will not trigger any errors at build
, oddly if there is a $ in the DATABASE_URL will still give these errors for the NEXT_PUBLIC_INVITE_URL, despite the $ being in the DB URL string

Edit (i can confirm $ can be used to expand a key in the .env file, shenanigans like this work)

 POSTGRES_HOST=localhost 
 POSTGRES_USER=bacon
 POSTGRES_PORT=5432
 POSTGRES_PASSWORD=""
 POSTGRES_DB_NAME=master-bot

DATABASE_URL="postgresql://$POSTGRES_USER:$POSTGRES_PASSWORD@$POSTGRES_HOST:$POSTGRES_PORT/$POSTGRES_DB_NAME?schema=public"

Much Love
-Bacon

from master-bot.

Howdy, was able to replicate this error message

Make sure the .env is in the root folder, and run npm run dev in root folder.

I get this error when I try to start the dashboard and bot separately with .env in the wrong folder

noticed the first command in log is not "npm run copy-env && concurrently "npm run dev:dashboard" "npm run dev:bot" in log, strongly indicates npm run dev was not ran in root folder

I hope this helps

Much Love -Bacon

This, make sure your .env file is in the root folder of the project

from master-bot.

This should be correct :?

from master-bot.

Yep yep, that is the correct place for the .env,
I'm not sure why the src folder is there tho. Maybe try cloning the repo to a new folder, and copy over your .env, and run the npm i, then npm run dev, and see if you get this error again.

I am curious if this is from a git pull that possibly failed

Much Love
-Bacon

from master-bot.

I think there was a problem after I cloned the repo in the past. Yesterday I wanted to update and run the new bot. That seemed to run with no problems.

I deleted the directory and cloned the repo again. Now the source folder is gone, but the problem still exists.

from master-bot.

@TrueMB Does your .env look like .env.example?
You have files that are not in the repo like start_Masterbot.sh and you shouldn't be running the bot in this way. If you clone the repo and follow the readme you will get the bot running in a short time

from master-bot.

Yes, I followed the instructions as far as I could understand it.
I copied the values from the .env file also in a new copy of the .env.example, since I wasn't sure, if it was the newest. Ofc I renamed it again .env.
I also use in my tests the named command above. I plan in the future to start the bot through a screen command (this is what the file does), but not yet.

from master-bot.