Open chrissooo opened 3 years ago
Hi, you are right ... after waiting a while, now its work ... maybe cache or something?
Hi again,
today not working again. Nothing changed since yesterday. Same Error like in first post.
Just install 6.4.608 again, no problems anymore.
I have a feeling that it has nothing to do with richdocumentscode.
fresh install, x86 pc, debian 64 bit, docker image, same problem
I also ran into this issue on nextcloud 20.0.8 ("Could not find urlsrc in WOPI"). At first I tried downgrading Collabora Online - Built-in CODE Server from 6.4.705 down to 6.4.608 release by release but Collabora Online was not working. Next I upgraded the CODE Server back to 6.4.705 and tried downgrading Collabora Online from version 3.7.17. And right away version 3.7.16 was working again.
Collabora Online 4.0.4, Collabora Online - Built-in CODE Server 6.4.608 on Nexcloud 21 work without problems
Have test a another constalation: Collabora Online 4.0.3 an Built-in CODE Server 6.4.705 work also...
Hi again, sorry for this mutch reporting, but the constalation "Collabora Online 4.0.3 an Built-in CODE Server 6.4.705" dont work today anymore. The only one konstalation thats work for longer time ist for me: "Collabora Online 4.0.4, Collabora Online - Built-in CODE Server 6.4.608"
Hi,
Same issue here, running Nextcloud 20.0.7 (latest snap available), made the mistake of upgrading Collabora Online to 3.7.17 and Built-in CODE Server to 6.4.705, and getting the same issue as the original post.
Not a critical issue as it's a test of Nextcloud used only by 2 persons, but still pretty annoying :/
@ppascher : I'm pretty new to NC, how did you downgrade to Collabora Online to 3.7.16 version ? Manual deployment from zip ? Cross-restore of a VM backup and manual copy of needed files ?
@dsysvdu I was wondering the same thing and basically tried what you proposed. Here are the steps:
custom_apps
folder that is located right below the root folder of your Nextcloud installationwget
for exampletar -xzf richdocuments.tar.gz -C .
./occ app:enable richdocuments
as www-data
user (i.e. you might need to prefix the previous command with sudo -u www-data
Now in the admin web UI of your Nextcloud server, you should see Collabora showing up as an available app update and when you try to open a document it should be working again. At least it did work for me :wink:
@FMeinicke Thank you very much for this detailed procedure, I'm sure that it will help many :)
I'll try this in the coming days and edit this post to tell the result (but I'm confident it will work)
@FMeinicke thanks for the instruction. Unfortunately NextCloud insist on autoupdating, but even without that a downgrade did not seem to help in my case. More tips appreciated!
Hi. Nextcloud snap 20.0.9 / Collabora Online 3.7.19 / CODE 6.4.705. Ubuntu 20.04 Fresh install Same pb...
@FMeinicke Thank you very much I tried your solution on my Nextcloud V21.0.1 both with downgraded versions of collabora V3 (not compatible) and V4. Unfortunately the problem persist again
I got the same error, running Nextcloud 21.0.2 Collabora Online v4.1.1 Collabora Online - Built-in CODE Server v6.4.806
installed the 2 app within NC, didn't work.
same
I have received the message mod_fcgid: stderr: richdocumentscode (proxy.php) error exit, PID: 212444, Message: exec_disabled
Is it neccessary that I activate the function exec that it is working?
I've the same problem on a fresh install on centos. When I disable selinux (setenforce 0) it is working
Can confirm that solves the problem for me also on Fedora 33 Server and running NextCloud 21.0.3.
Not for me. By default selinux in my case is disabled, and today I have updated Collabora to 4.2.1.
Getting the same issue using NC22, Collabora Online - Built-in CODE Server (6.4.1004), Collabora Online (4.2.1)
Exception: Could not find urlsrc in WOPI
Same issue here (NC 21.0.3, CO 4.2.1, CODE 6.4.1004): "Collabora Online server is reachable." but when opening a document, I always receive this message: "Failed to load Collabora Online - please try again later". Logging reports "Exception: Could not find urlsrc in WOPI". Had a lot of different combinations installed, but never got it working ... Tried with a docker collabora/code on DSM7, but this one was not able to get connected to it :-(
same problem Exception: Could not find urlsrc in WOPI
Update: never mind, after restarting and having SeLinux off, it started working again...
turning off selinux no longer works for me and "Exception: Could not find urlsrc in WOPI" is back again after I updated the app.
On my installation there was 2 Problems. One was selinux. I had to set own rules with ausearch -c 'AppRun' --raw | audit2allow -M my-AppRun
After updating nextcloud and the apps, I got the same error message and in my Browser Console there was
Refused to send form data to 'http://nextcloud.*****.de/apps/richdocumentscode/proxy.php?req=/loleaflet/2afbc52/loleaflet.html?WOPISrc=https%3A%2F%2Fnextcloud.******.de%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F3248_ocyhdvybdxcf&title=*******.ods&lang=de&closebutton=1&revisionhistory=1' because it violates the following Content Security Policy directive: "form-action 'self'
This problem was caused from my reverse proxy not sending all X-Forwarded Header to the nextcloud server.
This problem was caused from my reverse proxy not sending all X-Forwarded Header to the nextcloud server.
Would you mind sharing what exactly you have changed in your proxy config? I'm suspecting that I have the same problem, but it's quite hard to reproduce (only some users see it).
This problem was caused from my reverse proxy not sending all X-Forwarded Header to the nextcloud server.
I'm also very curious what you did because I have the exact same problem!
Would you mind sharing what exactly you have changed in your proxy config? I'm suspecting that I have the same problem, but it's quite hard to reproduce (only some users see it).
Here my settings (Apache/2.4). The important thing was the line with 'RequestHeader'
<VirtualHost *:443>
ServerName nextcloud.xxxxx.de:443
ProxyRequests Off
ProxyPreserveHost On
ProxyPass "/" "http://192.168.111.222/"
ProxyPassReverse "/" "http://192.168.111.222/"
RequestHeader set X-Forwarded-Proto https
@martinr63: thank you very much for your reply!
What was the reason that you thought it also had something to due with SELinux? Did you get AVC denial messages?
I added the directive RequestHeader set X-Forwarded-Proto https
but it didn't have any effect. When I look in /var/log/audit/audit.log
or /var/log/messages
I don't see any AVC denial messages.
What was the reason that you thought is also had something to due with SELinux?
I got tons of AVC denial messages in journalctl after installing setroubleshoot. Then I disabled selinux temporally, edited a document and did a ausearch | audit2allow
Same issue for me. Ubuntu Core 18 on Intel Nuc with NC, run as an appliance. Nextcloud snap 22.1.1snap2 Collabora online 4.2.3 Collabora CODE server 6.4.1103.
I think re-installing older versions is not a realistic option on this set up.
Here my settings (Apache/2.4). The important thing was the line with 'RequestHeader'
Thanks @martinr63! I'm using nginx-proxy which already has RequestHeader set X-Forwarded-Proto https
in place. So the issue must be elsewhere.
Faced this problem when using Colabora online
, Colabora online
simply did not open documents and writing to the logs:
{
"reqId": "YYw1753eVu93R4XFJoPuBgAAAE0",
"level": 3,
"time": "2021-11-10T21:13:21+00:00",
"remoteAddr": "**************",
"user": "*********",
"app": "richdocuments",
"method": "GET",
"url": "/index.php/apps/richdocuments/index?fileId=623652&requesttoken=8Xx%2FfJDIA27PkhonYID60rPpIxReqkYoIbnsmiJgF4c%3D%3AxRsaV%2FKyYQWm4GtlN%2FiyneCaSUIbxjJSb8672GAOZs8%3D",
"message": "Could not find urlsrc in WOPI",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:94.0) Gecko/20100101 Firefox/94.0",
"version": "22.2.0.2",
"exception": {
"Exception": "Exception",
"Message": "Could not find urlsrc in WOPI",
"Code": 0,
"Trace": [{
"file": "/var/www/nextcloud/apps/richdocuments/lib/TokenManager.php",
"line": 202,
"function": "getUrlSrc",
"class": "OCA\\Richdocuments\\WOPI\\Parser",
"type": "->"
}, {
"file": "/var/www/nextcloud/apps/richdocuments/lib/Controller/DocumentController.php",
"line": 222,
"function": "getToken",
"class": "OCA\\Richdocuments\\TokenManager",
"type": "->",
"args": ["*** sensitive parameters replaced ***"]
}, {
"file": "/var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php",
"line": 217,
"function": "index",
"class": "OCA\\Richdocuments\\Controller\\DocumentController",
"type": "->"
}, {
"file": "/var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php",
"line": 126,
"function": "executeController",
"class": "OC\\AppFramework\\Http\\Dispatcher",
"type": "->"
}, {
"file": "/var/www/nextcloud/lib/private/AppFramework/App.php",
"line": 156,
"function": "dispatch",
"class": "OC\\AppFramework\\Http\\Dispatcher",
"type": "->"
}, {
"file": "/var/www/nextcloud/lib/private/Route/Router.php",
"line": 301,
"function": "main",
"class": "OC\\AppFramework\\App",
"type": "::"
}, {
"file": "/var/www/nextcloud/lib/base.php",
"line": 1000,
"function": "match",
"class": "OC\\Route\\Router",
"type": "->"
}, {
"file": "/var/www/nextcloud/index.php",
"line": 36,
"function": "handleRequest",
"class": "OC",
"type": "::"
}
],
"File": "/var/www/nextcloud/apps/richdocuments/lib/WOPI/Parser.php",
"Line": 59,
"CustomMessage": "--"
},
"id": "618c41d2c7294"
}
The problem was solved by restarting memcached (sudo systemctl restart memcached
)
I solved the problem and you can find my solution in this issue.
Summary:
RequestHeader set X-Forwarded-Proto https
to my virtual host.In my case the problem was that the Collabora_Online.AppImage could not be started. I found this out by checking the apps/richdocumentscode/proxy.php?status
URL.
Hello, when using a snap of nextcloud, we could not normally change the config files. So how to make it work?
Hello, when using a snap of nextcloud, we could not normally change the config files. So how to make it work?
I have the same question.
hi, I am also experimenting this problem. Is there a way to fix it when using the snap ?
In my case I have a docker-based setup and no SELinux. The issue still occurs sometimes. Sometimes it works fine, though.
Which Linux distribution are you using?
Ubuntu server 20.04. But my problem is I am using the snap and I have no idea how to modify it to modify the configuration there.
Maybe you can ask the question at the forum of Snapcraft?
To answer my own question, with the snap it is enough to add @Verhoeckx's solution at the .htaccess
file, at /var/snap/nextcloud/current/nextcloud/config
:)
You mean you added the line RequestHeader set X-Forwarded-Proto https
to the .htaccess file?
yes, I made that and I got it working on nextcloud-snap :)
yes, I made that and I got it working on nextcloud-snap :)
Does not work for me... where exactly should the line be added?
This is my /var/snap/nextcloud/current/nextcloud/config/.htaccess
file:
# Section for Apache 2.4 to 2.6
<IfModule mod_authz_core.c>
Require all denied
</IfModule>
<IfModule mod_access_compat.c>
Order Allow,Deny
Deny from all
Satisfy All
</IfModule>
# Section for Apache 2.2
<IfModule !mod_authz_core.c>
<IfModule !mod_access_compat.c>
<IfModule mod_authz_host.c>
Order Allow,Deny
Deny from all
</IfModule>
Satisfy All
</IfModule>
</IfModule>
# Section for Apache 2.2 to 2.6
<IfModule mod_autoindex.c>
IndexIgnore *
</IfModule>
this is mine, and it works for me:
# Section for Apache 2.4 to 2.6
<IfModule mod_authz_core.c>
Require all denied
</IfModule>
<IfModule mod_access_compat.c>
Order Allow,Deny
Deny from all
Satisfy All
</IfModule>
# Section for Apache 2.2
<IfModule !mod_authz_core.c>
<IfModule !mod_access_compat.c>
<IfModule mod_authz_host.c>
Order Allow,Deny
Deny from all
</IfModule>
Satisfy All
</IfModule>
</IfModule>
# Section for Apache 2.2 to 2.6
<IfModule mod_autoindex.c>
IndexIgnore *
</IfModule>
RequestHeader set X-Forwarded-Proto https
Hi,
have Update to 6.4.705 an have a error when try to open a document:
I am on a CentOS 7 installation, PHP 8 and Apache. No Docker Image.
Manual Downgrade to 6.4.608 Fixed it.