全新安装后无法访问collabora

我已经安装了Ubuntu 16.04，并已安装nextcloud /var/www/cloud（wordpress位于根目录中）。它已经运行了一段时间了，但是我最近发现了collabora作为google docs的替代品，并且真的希望它能正常工作。尝试打开文档时，出现“禁止访问”错误。我已根据此处的说明安装了collabora

我检查了lsof -i的输出，可以看到docker在9980上侦听，在Nextcloud中配置了URL，老实说，我不太确定如何着手解决此问题。如果社区中的任何人可以给我一些指导，那将是惊人的。下面是一些其他信息。

来自/ var / log / apache2中的apache error.log的条目：

[Mon Jan 02 22:05:30.027625 2017] [authz_core:error] [pid 26396] [client <IPADDRESS>:54120] AH01630: client denied by server configuration: /var/www/html/cloud/data/.ocdata
[Mon Jan 02 22:05:32.314370 2017] [authz_core:error] [pid 3122] [client <IPADDRESS>:54123] AH01630: client denied by server configuration: /var/www/html/cloud/data/.ocdata

协作版本vhost的My Apache配置的已消毒版本：

<VirtualHost *:443>
  ServerName sub.domain.com:443

  # SSL configuration, you may want to take the easy route instead and use Lets Encrypt!
  SSLEngine on
  SSLCertificateFile /etc/letsencrypt/live/domain.com/fullchain.pem
  SSLCertificateKeyFile /etc/letsencrypt/live/domain.com/privkey.pem
  SSLProtocol all -SSLv2 -SSLv3
  SSLCipherSuite             ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA$
  SSLHonorCipherOrder on

  # Encoded slashes need to be allowed
  AllowEncodedSlashes     On

  # Container uses a unique non-signed certificate
  SSLProxyEngine On
  SSLProxyVerify None
  SSLProxyCheckPeerCN Off
  SSLProxyCheckPeerName Off

  # keep the host
  ProxyPreserveHost On

  # static html, js, images, etc. served from loolwsd
  # loleaflet is the client part of LibreOffice Online
  ProxyPass /loleaflet https://127.0.0.1:9980/loleaflet retry=0
  ProxyPassReverse           /loleaflet https://127.0.0.1:9980/loleaflet

  # WOPI discovery URL
  ProxyPass    /hosting/discovery https://127.0.0.1:9980/hosting/discovery retry=0
  ProxyPassReverse           /hosting/discovery https://127.0.0.1:9980/hosting/discovery

  # Main websocket
  ProxyPassMatch    "/lool/(.*)/ws$" wss://127.0.0.1:9980/lool/$1/ws

  # Admin Console websocket
  ProxyPass /lool/adminws wss://127.0.0.1:9980/lool/adminws

  # Download as, Fullscreen presentation and Image upload operations
  ProxyPass   /lool https://127.0.0.1:9980/lool
  ProxyPassReverse           /lool https://127.0.0.1:9980/lool
  ServerAlias    sub.domain.com
</VirtualHost>

我的nextcloud实例的地址是 domain.com/cloud

lsof -i的输出| grep docker我相信这表明docker容器正在侦听来自9980上本地主机的流量以发送到该容器

docker-pr  1634     root    4u  IPv4  19492      0t0  TCP localhost:9980 (LISTEN)

理论：我有一个理论，这次我可能需要再次设置nextcloud，因为nextcloud在webroot中，而我的博客在webroot内的文件夹中，因为我从文档中获得的氛围是nextcloud应该是在具有自己的域名的自己的计算机上，并且此服务连接到该根域名的子域。因此domain.com/cloud将整个过程都丢了一个循环

如果有人可以给我一些指导，我将不胜感激，因为nextcloud是我非常有兴趣投资的产品。

Mike Griffen的帖子仅解决了这个问题，它似乎是一个简单的解决方案。

Authz_core:error Client Denied by Server Configuration

... mod_authz_core是在Apache2.3中引入的。这改变了访问控制的声明方式

从：

Order allow, deny
Allow from all

至：

Require all granted

这意味着目录的总配置现在如下所示：

<Directory /path/to/directory>
     Options FollowSymlinks
     AllowOverride none
     Require all granted
</Directory>

重新启动apache，一切都会很好。