yes and there is additional one to the one you spotted already. The scheme is wrong: CODE generated http.//nc.. URL but it must do https://nc..
from: Making sure you're not a bot! I see they recommend additional headers like this:
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
but their config is completely different - my Nginx knowledge is not enough to judge if required - maybe you should check which headers you need to add to properly inform the backend that reverse proxy does TLS termination (likely built-in CODE doesn’t take overwriteprotocol into account). HTTP_X_FORWARDED_PROTO could do the trick..
Check Github issues - maybe you find a solution.. e.g.
- APP generates wrong URL · Issue #1497 · nextcloud/richdocuments · GitHub
- Saved with error: Collabora Online should use the same protocol as the server installation. · Issue #752 · nextcloud/richdocuments · GitHub
- Wrong proxy url being detected if running behind a reverse proxy · Issue #2 · CollaboraOnline/richdocumentscode · GitHub
- https://www.nginx.com/blog/websocket-nginx/
Brave log still expose your internal hostname for some reason (maybe delete cache?):
Update: this post describes in little cumbersome way richdocuments/CODE heavily relyes on proxy headers.. definitely try adding headers described above.. would be great you post the config once it works