Replies: 3 comments
-
|
I have the same problem. Possibly related to #401 |
Beta Was this translation helpful? Give feedback.
-
|
As @vijay-prema mentioned, related to #401, and also #796. This is caused by the users' individual tokens not being valid, rather than the master key. You should be able to fix it by creating a new wanderer user (which should work fine), and then in pocketbase copy its token from the new user to the old user. That should get your old user working again. |
Beta Was this translation helpful? Give feedback.
-
|
As development seems to have re-commenced, is there any update on this issue? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Because I changed my installation I also changed the Meilisearch API key. However, now if I try to access Wanderer web, I can no longer view my tracks. The log shows that Wanderer is using a wrong API key.
The environment variable is correctly set
MEILI_MASTER_KEY=my_keyand e.g. querying Meili with
curl -X GET localhost:7700/keys -H "Authorization: Bearer my_key"also works.
I also let Linkwarden access the same Meili instance and the changed master key was only a change of the corresponding value in Linkwarden's settings.
Is there something else in Wanderer I have to change in Wanderer if the Meilisearch API key is changed?
Beta Was this translation helpful? Give feedback.
All reactions