-
Notifications
You must be signed in to change notification settings - Fork 55
api key headaches #37
Comments
@JSv4 Any thoughts? I'm experiencing the same problem. The UI fails silently. The error is: |
Hey @ProgramItUp, this is a bug, but shouldn't be impacting collection creation. The REST API (not the websocket) has an optional API_KEY auth instead of a JWT token. It looks like it's still throwing an error message even when the JWT auth works. I don't think this is actually affecting anything. Obviously something that should be fixed, but I'm pretty sure you can ignore this. Is the applications working apart from this message? |
Hi @JSv4, thanks. I am not able to use the application. I’m hoping we can figure out what the bug is. |
Bump - I have the same issue! |
Thanks, everyone. I'm working on a number of fixes, this included. |
Same issue here |
Same issue. Any fixes yet? Thank you. |
You're welcome to test my PR that should fix this @rainwala @a-romero @nima-airbus @ProgramItUp |
Same issue here, any updates? |
You don't need to ask if there are any updates, you can check the repo commit history and see. Also see https://github.com/JSv4/Delphic/pull/85/files for how to fix it yourself. |
Hi
I managed to get it up and running fairly easily on a M1 Mac.
the only issue I'm having is that when I go to index a newly uploaded collection
it seems that there is an issue with API key authentication
I'm working with a known good OpenAI key
delphic_local_flower | INFO 2023-05-03 19:50:58,704 mixins 112 281472944230880 Connected to redis://redis:6379/0
delphic_local_django | API KEY authenticatE: yaddah
delphic_local_django | WARNING 2023-05-03 19:51:10,506 api_key 1yaddah INVALID KEY! - Error: APIKey matching query does not exist.
delphic_local_django | API KEY: None
delphic_local_django | INFO: 172.18.0.1:34644 - "GET /api/collections/available HTTP/1.1" 200 OK
The text was updated successfully, but these errors were encountered: