Replit Database Returns 403 ['invalid token']

Support Bug Reports
1

Problem description:
I was using Replit DB just fine yesterday with NodeJS, i boot up again this morning and I’m getting the issue described in the title. I’ve not changed anything since shutting down last night.

Expected behavior:

await client.list()

Returns the list of keys inside of my Replit DB, this was working perfectly last night.

Actual behavior:

[ 'invalid token' ]

Steps to reproduce:
Trigger any Replit DB function from @replit/database

Bug appears at this link:
My replit URL, i’m unable to share this…

Browser/OS/Device:
Windows 10

1 Like
2

Is it a private repl?

Replit.db is known to be buggy, do any of the other functions work?

1 Like
3

My Repl is public, although i’m under the impressed that my $REPLIT_DB_URL Should be kept secret, I’m pretty new to replit, I’m unaware of the consequences if i share this URL.

Replit.db is known to be buggy, do any of the other functions work?

All of the functions return the same, even when accessing them directly in the repl shell, for example:

curl "$REPLIT_DB_URL?prefix=*"

Returns:

invalid token

Navigating to the URL directly also display “invalid token” + a 403 status in the network tab

4

Afaik it won’t work on the cover page, the cover page would have it’s own DB, not related to yours, so it is ok to share.

Try running kill 1 and if that does not work fork the repl.