/uploadfile 401 Unauthorized (Invalid Authorization credentials)

[jackgofff]

I logged in side by side on both my localhost (Firebase successfully registering and configured in client/next-web/.env) and the realchar.ai site. Problem: cannot create characters on localhost

On my localhost: I am concurrently running the server via python cli.py run-uvicorn and client via cd client/next-web && npm install && npm run dev . When I try to create a character, I get these errors for /uploadfile (same applies to the /system_prompt, create_character, and upload_image ):

--------- VS-----------

On the realchar.ai live site:

Creating character works without issue.

💡initial ideas (?): - related to Request URL? ( http://127.0.0.0.1:8000/uploadfile vs https://api.realchar.ai/uploadfile) - Enviornment configurations / variables - Token refresh logic (see below)

One difference I see the token?key=.... row circled in red, both the Headers and the Payload:

[y1guo]

Hi Jack, glad to help!

/uploadfile sends your file to a GCP storage bucket. To use it locally, you'll need to get your own GCP storage bucket, and configure it in .env. A google_credentials.json file is also needed to prove your admin. Put the file under root directory of repo, and also enable GOOGLE_APPLICATION_CREDENTIALS=google_credentials.json in .env. It should work.

[jackgofff]

Ty! I got it to work! A few questions:

• I am working on the codebase I cloned 1week ago (before the latest changes with Rebyte). Will I have issues (I am a paying Rebyte member and love it, but for this project I would like to use without Rebyte)? If there are things I should know, lmk
• I want to fully self-host this project. After setting up the Firebase, GCP bucket, I believe next step is configuring Nginx and then Kubernetes. Is there anything else in the stack / backend infrastructure you guys are using for the realchar.ai public live site and if so, what is the path I should take forward?