@dev0 sorry misunderstood you in this case!
anyone has an idea where to gather the neccessary logs to forward these to the devs?
because like @ftaut said, its pretty much random where it works and where not - even uninstalling all the images and packages didnt help at all.
@victorbw in my case the logs didnt help me anyway. Anything seemd to be normal.
You can get the container log via docker logs id-of-your-instance
same! logs didnt help at allā¦ now how can we fix that?
As I read through the forums, yet nobody got collabora 2 running with nginx-proxy or haproxy. Use Apache.
wellā¦ thats odd ā¦ im using apache 
I think you and the TC are having different issues, did you check the browser console?
@dev0 this is the only output ive got from firefox, not sure if its related to it at all:
Content Security Policy: Die Direktive āframe-srcā sollte nicht mehr verwendet werden. Bitte verwenden Sie stattdessen die Direktive āchild-srcā. (unbekannt)
JQMIGRATE: Migrate is installed, version 1.4.0 jquery-migrate.min.js:2:542
JQMIGRATE: Migrate is installed, version 1.4.0 jquery-migrate.min.js:2:542
yeah, its german, shall i translate it? 
no thanks i am from austria, as I hat that issue firefox told me that he blocked the other part of the mixed content.
hi neighbour 
which leaded to the same result (access forbidden)?
i had a mixed content issue, in my case http nextcloud inside a LAN and https collabora.
@dev0 could you please provide us what the error was and how youāve solved it? some people might be looking for this as well 
in my case I used in the beginning http only in nextcloud for testing, that didnāt work with collabora because that part was https. So you need to use https for both, and the best with a public recognized certificate. You only can use http and http OR https and https. The recent versions of common browsers refuses render mixed content.
As collabora only supports https in the docker container you have to use https for the NC too.