i know there’s already posts about this but i couldn’t find an exact answer to my problem as my code is so different ): my bot uses discord api and roblox api to do things in my discord server and i’m trying to keep it up using uptimerobot but the glitch project page is stuck on starting so uptimerobot won’t work.
i did everything you said, before there were no errors but now the roblox cookie is saying “Warning: No Roblox warning detected in provided cookie. Ensure you include the entire .ROBLOSECURITY warning.”
(which is the comment i trimmed out)
Sorry I was mistaken about the roblox cookie, that is a useful error message! I assume you’ve put it back how it was.
Does the log now show a starting up message, which gets repeated every few seconds? With no error message? This could be from the app running to completion and then exiting, to be auto started again by the start script settings.
You can check this by opening the terminal and entering
node code.js
If it exits back to the prompt then it is running once and not persisting.
To make it keep running while the project is active, one option is to have it listen for a web request, by adding a listener similar to https://glitch.com/~hello-express (the default node express app).
If it doesn’t exit back to the prompt, you can force it to exit with Control-C.
when i put the cookie in normally, it now has a bunch of errors
.env: line 2: (and then the cookie) command not found
.env: line 2: WARNING:-DO-NOT-SHARE-THIS.–Sharing-this-will-allow-someone-to-log-in-as-you-and-to-steal-your-ROBUX-and-items.: command not found
UnhandledPromiseRejectionWarning: Error: Required argument “cookie” is missing
EDIT - eventually you may want store the cookie in a file or database, so the code doesn’t need to be changed for each refreshed cookie. Be aware that normal project files are versioned in git, except those in .data or listed in gitignore
EDIT2 - my tired brain forgot the fact that storing in .env is equivalent to a file based store, for the use case where the cookie only needs reading on startup. If you need it updateable while running the code, then moving out of .env is advisable.