Troubleshooting

Passing authentication headers

If your underlying Hasura DDN project utilizes JWTs or a webhook for authentication, you can pass the appropriate values by clicking the Auth button on the left-hand side of the chat dialogue when starting a new thread. To learn more about authentication and Hasura DDN, check out the docs.

LLM Response errors

Error streaming from LLM: Illegal header value b’Bearer

This error happens when the PromptQL playground has not been started with a PromptQL Secret key.

This typically indicates that a DDN project was not initialized with the local project or the project does not have an associated PromptQL Secret key.

To check if the project was initialized, run this in the project directory:

ddn context get project
Case 1: Project has not been initialized

If you get the error Key "project" is not set., you need to initialize a DDN project.

Run the following command in the project directory:

ddn project init

Restarting the local services post this should fix the issue.

Case 2: Project has been initialized but does not have a PromptQL Secret key

If you already have a project initialized, you might need to generate the PromptQL Secret key for the project.

Run the following command in the project directory to generate a PromptQL Secret key:

Make sure you have the latest version of cli.
ddn auth generate-promptql-secret-key

Restarting the local services post this should fix the issue.

Error streaming from LLM: Client error ‘403 Forbidden’ for url https://llm.promptql.pro.hasura.io/stream For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403

This error happens when the PromptQL playground has been started with an invalid PromptQL Secret key.

This typically happens if an existing PromptQL Secret key is deleted or becomes invalid.

Run the following command in the project directory to generate a new PromptQL Secret key:

Make sure you have the latest version of cli.
ddn auth generate-promptql-secret-key

Restarting the local services post this should fix the issue.