[GH-ISSUE #3494] [BUG]: Confluence Connector not working for self-hosted Confluence server #2256

Closed
opened 2026-02-22 18:28:51 -05:00 by yindo · 3 comments
Owner

Originally created by @markkofler on GitHub (Mar 18, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3494

Originally assigned to: @shatfield4 on GitHub.

How are you running AnythingLLM?

Docker (local)

What happened?

Unfortunately I am not able to connect to our self-hosted Confluence servers when using the Confluence Connector. The logs show the following error:

[collector] error: Error: Error: Failed to fetch https://confluence.example.com/rest/api/content?spaceKey=AIINFRA&limit=25&start=0&expand=body.storage,version from Confluence: Error: Failed to fetch https://confluence.example.com/rest/api/content?spaceKey=AIINFRA&limit=25&start=0&expand=body.storage,version from Confluence: 403
    at ve.fetchConfluenceData (/Applications/AnythingLLM.app/Contents/Resources/backend/collector.js:36:6340)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ve.fetchAllPagesInSpace (/Applications/AnythingLLM.app/Contents/Resources/backend/collector.js:36:6579)
    at async ve.load (/Applications/AnythingLLM.app/Contents/Resources/backend/collector.js:36:5904)
    at async Cs (/Applications/AnythingLLM.app/Contents/Resources/backend/collector.js:42:1102)
    at async /Applications/AnythingLLM.app/Contents/Resources/backend/collector.js:42:9628

My first guess is when testing with curl, the wrong URL is used by the connector for on-prem Confluence. Because if I test the following command, it works fine:

curl -u username:"password" "https://confluence.example.com/rest/api/content/search?cql=space=AIINFRA&limit=25&start=0&expand=body.storage,version"

This would also be the way how to do it based on the Confluence API documentation: https://developer.atlassian.com/server/confluence/rest/v1000/intro/#how-to-perform-an-advanced-search

Any way this can be changed, or you see anything else that is wrong with my config?

Are there known steps to reproduce?

Configure the Confluence Data Connector with deployment type "Self-hosted".

Originally created by @markkofler on GitHub (Mar 18, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3494 Originally assigned to: @shatfield4 on GitHub. ### How are you running AnythingLLM? Docker (local) ### What happened? Unfortunately I am not able to connect to our self-hosted Confluence servers when using the Confluence Connector. The logs show the following error: ``` [collector] error: Error: Error: Failed to fetch https://confluence.example.com/rest/api/content?spaceKey=AIINFRA&limit=25&start=0&expand=body.storage,version from Confluence: Error: Failed to fetch https://confluence.example.com/rest/api/content?spaceKey=AIINFRA&limit=25&start=0&expand=body.storage,version from Confluence: 403 at ve.fetchConfluenceData (/Applications/AnythingLLM.app/Contents/Resources/backend/collector.js:36:6340) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async ve.fetchAllPagesInSpace (/Applications/AnythingLLM.app/Contents/Resources/backend/collector.js:36:6579) at async ve.load (/Applications/AnythingLLM.app/Contents/Resources/backend/collector.js:36:5904) at async Cs (/Applications/AnythingLLM.app/Contents/Resources/backend/collector.js:42:1102) at async /Applications/AnythingLLM.app/Contents/Resources/backend/collector.js:42:9628 ``` My first guess is when testing with curl, the wrong URL is used by the connector for on-prem Confluence. Because if I test the following command, it works fine: ``` curl -u username:"password" "https://confluence.example.com/rest/api/content/search?cql=space=AIINFRA&limit=25&start=0&expand=body.storage,version" ``` This would also be the way how to do it based on the Confluence API documentation: https://developer.atlassian.com/server/confluence/rest/v1000/intro/#how-to-perform-an-advanced-search Any way this can be changed, or you see anything else that is wrong with my config? ### Are there known steps to reproduce? Configure the Confluence Data Connector with deployment type "Self-hosted".
yindo added the Integration Requestpossible buginvestigating labels 2026-02-22 18:28:51 -05:00
yindo closed this issue 2026-02-22 18:28:51 -05:00
Author
Owner

@o-kima commented on GitHub (May 11, 2025):

I'm also experiencing this issue.
I think its related to docker nertwork configurations

when i run a curl command from my local environment it works:

curl -v "https://xxx.atlassian.net/wiki/rest/api/content?spaceKey=Payments&limit=25&start=0&expand=body.storage,version" -H "Authorization: Basic xxxx="

but when i run it in a docker i get an error:

$ docker exec -it b389c246e8cddaf5bbd146f0437df228c8d33f7a5179b6909014d155b8cb760d bash -c "sh"
$ curl -v "https://xxx.atlassian.net/wiki/rest/api/content?spaceKey=Payments&limit=25&start=0&expand=body.storage,version" -H "Authorization: Basic xxxx"
* Could not resolve host: xx.atlassian.net
* Closing connection 0
curl: (6) Could not resolve host: xxx.atlassian.net
@o-kima commented on GitHub (May 11, 2025): I'm also experiencing this issue. I think its related to docker nertwork configurations when i run a curl command from my local environment it works: ``` curl -v "https://xxx.atlassian.net/wiki/rest/api/content?spaceKey=Payments&limit=25&start=0&expand=body.storage,version" -H "Authorization: Basic xxxx=" ``` but when i run it in a docker i get an error: ``` $ docker exec -it b389c246e8cddaf5bbd146f0437df228c8d33f7a5179b6909014d155b8cb760d bash -c "sh" $ curl -v "https://xxx.atlassian.net/wiki/rest/api/content?spaceKey=Payments&limit=25&start=0&expand=body.storage,version" -H "Authorization: Basic xxxx" * Could not resolve host: xx.atlassian.net * Closing connection 0 curl: (6) Could not resolve host: xxx.atlassian.net ```
Author
Owner

@timothycarambat commented on GitHub (May 12, 2025):

Is https://xxx.atlassian.net on a local IP? If this is a custom host resolution on the machine this DNS resolution will not extend to the container and may need to be handled by a --network adapter for the docker container. That being said, if it is a local IP range than if the DNS is resolving - it would resolve to a local IP, which would then loopback into the container and not the host.

https://docs.anythingllm.com/installation-docker/localhost

@timothycarambat commented on GitHub (May 12, 2025): Is `https://xxx.atlassian.net` on a local IP? If this is a custom `host` resolution on the machine this DNS resolution will not extend to the container and may need to be handled by a `--network` adapter for the docker container. That being said, if it is a local IP range than if the DNS is resolving - it would resolve to a local IP, which would then loopback into the container and _not the host_. https://docs.anythingllm.com/installation-docker/localhost
Author
Owner

@o-kima commented on GitHub (May 13, 2025):

@timothycarambat The Docker is installed locally, but Confluence is not local, it is atlassian managed. everyone can access the URL.

@o-kima commented on GitHub (May 13, 2025): @timothycarambat The Docker is installed locally, but Confluence is not local, it is atlassian managed. everyone can access the URL.
yindo changed title from [BUG]: Confluence Connector not working for self-hosted Confluence server to [GH-ISSUE #3494] [BUG]: Confluence Connector not working for self-hosted Confluence server 2026-06-05 14:45:27 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2256