The same in both scenarios, fresh install and upgrade from v10.0.2
Data directory is set to /home/nextcloud/data with the appropriate permissions
The above directoy where included in apache settings
<Directory /home/nextcloud/data/>
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
and yet issue exist, please advice on error source
Same thing for me, updated to NC11 it was working alright, then updated “Collabora Online” app and I have Access forbidden.
Clean install didn’t help.
I guess don’t touch something that’s not broken rule applies here XD, JK
It’s Normal that the app : DESKTOP (bureau in french) is not visible anymore.
I don’t know what they do, but for the moment, it won’t be visible, the app lunch automaticly when you click on an office document.
For creating a new Doc - Spredsheet - Presentation you have to click on the + near the folder name.
Can you get the apache (or nginx) error log when you try to reach your page ?
nothing in the apache2 logs as well as NC11 logs, everything works as it should be… let me try not using external data folder.
–update: even with the official data folder I still get the same thing…(even after applying official permissions from the guideline)
–update2: I rolled back to NC10 and everything works fine
–update3: I think I have an idea why it happens:
I got this Loading documents when I clicked on the “office” in Apps in previous app. Then I updated collabora connector app, and in the new version I suspect that “Office” from apps is removed so I get access forbidden now.
This is how I see it in the previous Office connector app:
It could be true, i didn’t have it because i never installed yet Collabora on a brand new Nextcloud 11.
I started mine with a brand new Nextcloud 9 then updated at every new version. @vCentre : Could you try to install Nextcloud 10.0.2 first then upgrade it, and tell us if it works for you ?
When i had a port configured I was getting accessed denied. And obviously make sure you added a firewall rule if you have a firewall in the mix (which hopefully you do).
[Wed Dec 28 08:28:06.567050 2016] [authz_core:error] [pid 8400] [client my.public.ip:53238] AH01630: client denied by server configuration: /var/www/nextcloud/data/.ocdata
[Wed Dec 28 08:28:30.848958 2016] [authz_core:error] [pid 8400] [client my.public.ip:53254] AH01630: client denied by server configuration: /var/www/nextcloud/data/.ocdata
[Wed Dec 28 08:36:06.087290 2016] [proxy_http:error] [pid 8399] (103)Software caused connection abort: [client my.public.ip:53328] AH01102: error reading status line from remote server 127.0.0.1:9980
[Wed Dec 28 08:36:06.087442 2016] [proxy:error] [pid 8399] [client my.public.ip:53328] AH00898: Error reading from remote server returned by /hosting/discovery
[Wed Dec 28 13:49:22.466616 2016] [proxy_http:error] [pid 8398] (103)Software caused connection abort: [client my.public.ip:54330] AH01102: error reading status line from remote server 127.0.0.1:9980
[Wed Dec 28 13:49:22.480593 2016] [proxy:error] [pid 8398] [client my.public.ip:54330] AH00898: Error reading from remote server returned by /hosting/discovery
[Wed Dec 28 13:49:22.574914 2016] [proxy_http:error] [pid 8468] (103)Software caused connection abort: [client my.public.ip:54332] AH01102: error reading status line from remote server 127.0.0.1:9980
[Wed Dec 28 13:49:22.575053 2016] [proxy:error] [pid 8468] [client my.public.ip:54332] AH00898: Error reading from remote server returned by /hosting/discovery
docker status
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since wo 2016-12-28 08:02:17 CET; 6h ago
Docs: https://docs.docker.com
Main PID: 1090 (dockerd)
Tasks: 27
Memory: 51.6M
CPU: 36.578s
CGroup: /system.slice/docker.service
├─1090 /usr/bin/dockerd -H fd://
├─1504 containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --shim containerd-shim --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --runtime runc
└─1826 /usr/bin/docker-proxy -proto tcp -host-ip 127.0.0.1 -host-port 9980 -container-ip 172.17.0.2 -container-port 9980
dec 28 08:02:03 cloud.domain.nl dockerd[1090]: time="2016-12-28T08:02:03.311160973+01:00" level=info msg="Loading containers: start."
dec 28 08:02:04 cloud.domain.nl dockerd[1090]: .time="2016-12-28T08:02:04.619026380+01:00" level=info msg="Firewalld running: false"
dec 28 08:02:08 cloud.domain.nl dockerd[1090]: time="2016-12-28T08:02:08.148302414+01:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
dec 28 08:02:10 cloud.domain.nl dockerd[1090]: time="2016-12-28T08:02:10.038287796+01:00" level=info msg="No non-localhost DNS nameservers are left in resolv.conf. Using default external servers : [nameserver 8.8.8.8 nameserver 8.8.4.4]"
dec 28 08:02:10 cloud.domain.nl dockerd[1090]: time="2016-12-28T08:02:10.038470291+01:00" level=info msg="IPv6 enabled; Adding default IPv6 external servers : [nameserver 2001:4860:4860::8888 nameserver 2001:4860:4860::8844]"
dec 28 08:02:16 cloud.domain.nl dockerd[1090]: time="2016-12-28T08:02:16.965128283+01:00" level=info msg="Loading containers: done."
dec 28 08:02:16 cloud.domain.nl dockerd[1090]: time="2016-12-28T08:02:16.980859543+01:00" level=info msg="Daemon has completed initialization"
dec 28 08:02:16 cloud.domain.nl dockerd[1090]: time="2016-12-28T08:02:16.982340737+01:00" level=info msg="Docker daemon" commit=23cf638 graphdriver=aufs version=1.12.1
dec 28 08:02:17 cloud.domain.nl systemd[1]: Started Docker Application Container Engine.
dec 28 08:02:17 cloud.domain.nl dockerd[1090]: time="2016-12-28T08:02:17.124154721+01:00" level=info msg="API listen on /var/run/docker.sock"
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
45bd544dcdbf collabora/code "/bin/sh -c 'bash sta" 7 hours ago Restarting (1) 2 hours ago 127.0.0.1:9980->9980/tcp distracted_hamilton
it seems everything is working but I still get access forbidden when I try opening a office document. I have no idea where to look but it seems something is not working right on the apache proxy module
Also is it correct that the modules proxy_http, proxy_wstunnel only have a .load and no .conf
If anyone would like to help me here and need insight of any configuration please do ask.
I’m still having the same issue as well… was curious if anyone has figured anything out yet? I removed NC and the Collabora app to start from scratch and I’m still getting the Access Forbidden.
it only accepts port 443, so you link has to be in this format: https://office.foo.com (even though in description it says “URL (and port)” – it’s a lie, it won’t work on a custom port, will throw this " access forbidden" error.
Try entering some other, wrong, address there. For example http://office.nextcloud.com then apply, then fix it back to your, correct, address.
hopefully it’ll help. Other than that I had the same problem on NC11 but I fixed it by rolling back to NC10, then updating to NC10.0.2 then NC11 and it sort of worked.
No dice for me… other than the fact that I didn’t roll back to 10 then back to 11 as backing up my NC takes quite awhile (the data folder specifically, not that you NEED to do this when it’s in a different location than the www HC folder, but I have way too important of stuff in there to not do so). I did however delete the Collabora container and redo all of that, to no avail such is life I guess, if I get the energy over the long weekend I may do that, was just really hoping not to, especially since this should really work as-is.
If I do get the energy than more than likely I’ll actually review all of the code to see what’s happening so it can be fixed for good and for everyone, there’s no reason why reverting back then up again should be the answer.
Edit: forgot to say thanks for the info depawlur
Edit 2: is anyone having this trouble that doesn’t have Strict Transport Security enabled? I always have mine on, and I’m now wondering if that’s the issue, which I will also test when I have time to change settings
I am using my own CA certificates and was having the same problem with the “Access Forbidden” message. I was able to get it working by adding my root CA certificate to the following file:
nextcloud/resources/config/ca-bundle.crt
You have to add the CA cert manually to ownCloud trusted cert storage:
installed and configured collabora plugin with my non standard https port
the collabora plugin it’s ok, I created a .odt file from button menu +
when I start to open the .odt document from nextcloud, I have an Access Forbidden (Accesso Negato) message, nothing appears into docker logs or nginx logs or nextcloud logs, apparently no errors…
now adding my selfsigned opemediavault.crt into nextcloud/resources/config/ca-bundle.crt I’m able to edit the .odt doc from nextcloud
@pmyork Thanx a lot for have shared your solution!