# Nextcloud and Collabora with Docker and WOPI requests allow list

**URL:** <https://help.nextcloud.com/t/nextcloud-and-collabora-with-docker-and-wopi-requests-allow-list/169373>\
**Category:** 📄 Office\
**Tags:** docker, collabora-online, dns, docker-compose\
**Created:** [September 3, 2023, 6:58am UTC](https://help.nextcloud.com/t/nextcloud-and-collabora-with-docker-and-wopi-requests-allow-list/169373 "2023-09-03T06:58:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [September 5, 2023, 8:57pm UTC](https://help.nextcloud.com/t/nextcloud-and-collabora-with-docker-and-wopi-requests-allow-list/169373/2 "2023-09-05T20:57:49Z")

</div>

I see the issue in my installation as well (despite using local Pi-Hole DNS), ~~but I never find motivation to dig deeper into the issue.~~ there must be an issue with DNS resolution between containers running on the same docker host but using public DNS names. Container settings like ~~[extra\_hosts](https://docs.docker.com/compose/compose-file/compose-file-v3/#extra_hosts) or~~ [ailas](https://docs.docker.com/engine/reference/commandline/network_connect/) could be the key.

UPDATE: in the meanwhile I managed to force traffic from Docker straight to the reverse proxy. see details in [this post](https://help.nextcloud.com/t/probably-dns-help-with-nc-docker-collabora-wireguard-tunnel/176562/5)

---

_[View the full topic](https://help.nextcloud.com/t/nextcloud-and-collabora-with-docker-and-wopi-requests-allow-list/169373)._