[install-help]: Is ad blocker stopping context chat?

Describe the issue
The backend is on one computer and the next cloud installation is on another. They are successfully communicating by way of the harp proxy But there are a few glitches I'm trying to work out. Sometimes the source loading process stalls and I have to restart the container for the backend and the front-end enabled/disabled in order to get moving again. After trial and error, my theory tells me that my pi-hole ad-blocker somehow prevents this loading process. So I've been turning it off and I find that the stall doesn't seem to persist as long.

We haven't yet passed the initial indexing, but it seems we made tremendous progress.

My question is how to configure the pi hole so that I can keep the ad blocker and not tamper the context chat backend adversely.

Context Chat Backend logs (if applicable, from the docker container)

Setup Details (please complete the following information):

• Nextcloud Version: AIO current
• AppAPI Version: current
• Context Chat PHP Version 5.3.1
• Context Chat Backend Version 5.3. dev
• Nextcloud deployment method: AIO
• Context Chat Backend deployment method: manual

Start by reviewing the repeated PUT /loadSources entries in the provided backend logs alongside the AIO, manual backend, and Pi-hole setup details. Done would mean identifying whether Pi-hole causes the source-loading stalls and documenting a configuration that preserves ad blocking without disrupting Context Chat.