Yes it was. May be, this is a working configuration for all kinds under docker systems.
I forget also settings in server hosts file (the main server, not the docker image) : nano /etc/hosts 127.0.0.1 localhost cloud.mydom.comoffice.mydom.com
Yes I suppose you could set your host names at the level of the hostās /etc/hosts file. Totally valid. I usually set hostnames at the router level since Iām a lot less likely to forget what Iāve done. I also have cloud and office on physically different VMās so itās easier for me to set the parameter at the router level. If they are on the same host, modification of /etc/hosts may be easier.
Things I see commonly as errors:
Donāt open firewall ports
Donāt set local resolution of domain names at the /etc/host or router level
Honestly Iāve never really done a packet capture with Collabora. I never really knew you could write an iptables rule based on country of origin. However you have your rule on the input chain (not output). This would imply you are receiving packets externally.
Iām thinking about my own setup. I have wide open input rules to the collabora port (just a generic pass all rule which I believe is being controlled ufw (which definitely isnāt as fine grained as an actual iptables rule)), however at the router level there are no port forwarding rules to allow external access. In fact on my nginx configuration, I only allow LAN IP address access to nextcloud. All my docs open in Collabora (locally). Perhaps your iptables rule is blocking more than what it should?