You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When I want to login on the developer dashboard, I receive the following error message:
The login and all other RAG functionalities worked without a problem on the previous day. When I checked the logs of the docker container, the following lines caught my attention:
So it seems like there is an issue with how the access tokens are refreshed. Before that error occured, the access token is refreshed periodically in the Docker logs and after the error, there is no attempt to refresh the access tokens anymore.
This is the second time that this situation happend to me. The first time, I needed to restart the docker container with
r2r docker-down
r2r serve --docker
to being able to login again. However, all uploaded documents, created users, and updated passwords were gone and it was basically like a facroty-reset of the RAG server.
RAG Server:
OS: Ubuntu 24.04 LTS
Laptop:
OS: Ubuntu 22.04.5 LTS
Browser: Google Chome (Version 129.0.6668.70 (Official Build) (64-bit))
The text was updated successfully, but these errors were encountered:
Hey there, this is not an expected behavior—especially that all of your files were missing after running r2r docker-down.
Can you confirm the following:
Version of R2R
How you started R2R instance (is there a custom config, and depending on your version did you change and Postgres environment variables related to vecs/collections/projects)?
I did not use a custom config to start the R2R instance. I used all the default settings and then the r2r serve --docker to start the instance. Also, I did not change any Postgres environment variables.
Description
When I want to login on the developer dashboard, I receive the following error message:
The login and all other RAG functionalities worked without a problem on the previous day. When I checked the logs of the docker container, the following lines caught my attention:
So it seems like there is an issue with how the access tokens are refreshed. Before that error occured, the access token is refreshed periodically in the Docker logs and after the error, there is no attempt to refresh the access tokens anymore.
This is the second time that this situation happend to me. The first time, I needed to restart the docker container with
to being able to login again. However, all uploaded documents, created users, and updated passwords were gone and it was basically like a facroty-reset of the RAG server.
RAG Server:
Laptop:
The text was updated successfully, but these errors were encountered: