mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
Add an External Knowledge API : LlamaCloud #836
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bfechoz-ade on GitHub (Nov 26, 2025).
Self Checks
Dify version
1.4.1
Plugin version
0.0.1
Cloud or Self Hosted
Cloud
Steps to reproduce
Add an External Knowledge API
I am adding my external LlamaCloud base to the plugin page with the api key and an api name who give me the endpoint that I am trying to add in the page for adding external knowledge base.
and then I found the error msg : "failed to connect to the endpoint: http://localhost/e/kbum3nr..pfiah25/retrieval"
WHEREAS I still have a functionnal endpoint working with my previous Llamacloud account with a US location but I had to change for a european one and now the linking is not working
✔️ Error log
failed to connect to the endpoint: http://localhost/e/kbum3nr..pfiah25/retrieval
@dosubot[bot] commented on GitHub (Nov 26, 2025):
The error happens because Dify is trying to connect to a 'localhost' endpoint, which isn't accessible in cloud deployments. This usually means the endpoint URL for your external knowledge API wasn't updated or saved correctly when you switched to the European LlamaCloud region.
To fix this, double-check that you are entering the full European LlamaCloud endpoint URL (starting with
https://...) in the Dify UI, and make sure to remove the/retrievalsuffix before saving it, as required by the LlamaCloud plugin instructions. If you still see the error, it's likely that Dify is defaulting to a template likehttp://localhost/e/{hook_id}/retrievalbecause the endpoint wasn't set or persisted properly in the backend settings.If you have access to environment variables (for self-hosted or advanced cloud setups), ensure that
ENDPOINT_URL_TEMPLATEis set to your public domain or IP (not localhost), for example:ENDPOINT_URL_TEMPLATE=https://your-domain.com/e/{hook_id}. After updating, restart all Dify services to apply the changes. This ensures Dify generates the correct URLs for plugin endpoints instead of defaulting to localhost [source 1] [source 2].If your LlamaCloud endpoint is only accessible on your local network, you’ll need to expose it to the public internet (using a tool like Ngrok or a public IP/domain) so Dify Cloud can reach it.
If you’re still having trouble, verify the endpoint value in the Dify UI or database, and try removing and re-adding the external knowledge API with the correct URL. Let me know if you need help with a specific endpoint format or network setup!
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other