Hi thanks for taking a look at this. Thinking on, I guess I may need to configure the nextcloud host and port somewhere (172.17.0.2:80) as the collabra container might be trying to reach localhost:8080 for webdav?
First the logs from the Nextcloud container (nothing new was logged by the Collabra container) - when it failed to open a document:
<storage desc="Backend storage">
<filesystem allow="false" />
<wopi desc="Allow/deny wopi storage." allow="true">
<max_file_size desc="Maximum document size in bytes to load. 0 for unlimited." type="uint">0</max_file_size>
<locking desc="Locking settings">
<refresh desc="How frequently we should re-acquire a lock with the storage server, in seconds (default 15 mins) or 0 for no refresh" type="int" default="900">900</refresh>
<alias_groups desc="default mode is 'first' it allows only the first host when groups are not defined. set mode to 'groups' and define group to allow multiple host and its aliases" mode="first">
<!-- If you need to use multiple wopi hosts, please change the mode to "groups" and
add the hosts below. If one host is accessible under multiple ip addresses
or names, add them as aliases. -->
<host desc="hostname to allow or deny." allow="true">scheme://hostname:port</host>
<alias desc="regex pattern of aliasname">scheme://aliasname1:port</alias>
<alias desc="regex pattern of aliasname">scheme://aliasname2:port</alias>
<!-- More "group"s possible here -->
<ssl desc="SSL settings">
<as_scheme type="bool" default="true" desc="When set we exclusively use the WOPI URI's scheme to enable SSL for storage"></as_scheme>
<enable type="bool" desc="If as_scheme is false or not set, this can be set to force SSL encryption between storage and coolwsd. When empty this defaults to following the ssl.enable setting"></enable>
<cert_file_path desc="Path to the cert file" relative="false"></cert_file_path>
<key_file_path desc="Path to the key file" relative="false"></key_file_path>
<ca_file_path desc="Path to the ca file. If this is not empty, then SSL verification will be strict, otherwise cert of storage (WOPI-like host) will not be verified." relative="false"></ca_file_path>
<cipher_list desc="List of OpenSSL ciphers to accept. If empty the defaults are used. These can be overridden only if absolutely needed."></cipher_list>
@rash419 Sorry, found what you were looking for, I think. There were no logs in docker for the Collabra container (and nothing new in /var/log), just the original final console message from startup:
wsd-00001-00001 2022-04-13 12:45:34.514423 +0000 [ coolwsd ] INF WSD initialization complete: setting log-level to [warning] as configured.| wsd/COOLWSD.cpp:4696
Ready to accept connections on port 9980.
However found the message below in the Nextcloud web console, in Administration → Logging.
Warning no app in context Host 172.17.0.3 was not connected to because it violates local access rules 2022-04-13T15:04:07+0100
There is some ACL configuration I need to do somewhere? I’m completely new to Nextcloud but liking what I see so far if I can get it working.
It has nothing new from the time of the errors, only the original container startup messages. I captured the whole set to a file but I’m not able to attach it here as I’m a new user. You can view it here instead. Looks to me like Nextcloud doesn’t want to talk to 172.17.0.3 according to the error message in the console?
I since tried adding 172.17.0.1/24 to the “brute force ip whitelist” but it didn’t work - still getting the same error in the console logs.
Also attached the logs from the Collabra container. I had to rename .txt as .doc to upload it. collabralog.doc (316.4 KB)
I created a docker network to be able to use resolvable hostnames instead of IP addresses.
$ docker network create --driver bridge collabora
$ docker run --name collabora --network collabora -t -d -p 9980:9980 -e "extra_params=--o:ssl.enable=false" --restart always collabora/code
$ docker run --name nextcloud --network collabora -t -d -p 8080:80 --restart always nextcloud
$ docker exec -t collabora cat /etc/coolwsd/coolwsd.xml | grep "SSL support"
<enable type="bool" desc="Controls whether SSL encryption between coolwsd and the network is enabled (do not disable for production deployment). If default is false, must first be compiled with SSL support to enable." default="true">false</enable>
$ docker exec -t nextcloud curl http://collabora:9980
This has got me past the “was not connected to because it violates local access rules” nextcloud UI logging errors but it still isn’t opening documents and the console logs are not providing any clues whether it actually reached collabora or not. The nextcloud logs after I click on a docx file (the sample one):