# "Unauthorized WOPI host" when opening documents in Nextcloud **URL:** \ **Category:** ℹ️ Support\ **Tags:** wopi, collabora-online, cloudflare, truenas\ **Created:** [August 23, 2025, 11:24pm UTC](https://help.nextcloud.com/t/unauthorized-wopi-host-when-opening-documents-in-nextcloud/230830 "2025-08-23T23:24:41Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [August 24, 2025, 7:14pm UTC](https://help.nextcloud.com/t/unauthorized-wopi-host-when-opening-documents-in-nextcloud/230830/2 "2025-08-24T19:14:29Z")
missing/failed connection from Collabora to Nextcloud is definitely a problem - I would focus on this issue. from your curl output connection from Collabora to NC goes to `192.168.1.3:443` which might be the “internal” IP of Nextcloud container - there must be more details related to the cert e.g. subject and SANs included in the cert so you can conclude where it comes from… as your real public certificate is hosted on NPM you want to connect there (and make it serve the request). I can’t tell you to configure this with TrueNAS but similar topic using plain Docker is discussed here [Probably DNS help with NC Docker + Collabora + Wireguard tunnel](https://help.nextcloud.com/t/probably-dns-help-with-nc-docker-collabora-wireguard-tunnel/176562/5) - you must ensure public domain resolves to the NPM inside of your container so the connection uses proper TLS cert rather direct connection between two containers (or maybe somewhere else).. --- _[View the full topic](https://help.nextcloud.com/t/unauthorized-wopi-host-when-opening-documents-in-nextcloud/230830)._