-
Notifications
You must be signed in to change notification settings - Fork 1
reva produce 404 status code when einstein send a file to marie #22
Comments
Hi @mrvahedi68, we noticed the same issue, we are unable to establish a share from NC to OC. A share entry is created in the originating Nextcloud database, but sending the share to the target Reva site (POST to originator's /ocm/send API) silently fails on 404. Nothing ever reaches the target site. The relevant logs from the originating Reva site are:
maybe @michielbdejong will have some idea on how to debug this? |
I'll have a look next week, thanks! |
@gmgigi96 can you please take a look together with @michielbdejong on this issue? |
I moved this issue from 'Planned' to 'Todo' in https://github.com/orgs/sciencemesh/projects/14/views/1?layout=board |
Moved it from 'Todo' to 'In progress'. |
Trying to reproduce this using ocm-test-suite and improved reva error messaging, temporarily using mesh.pondersource.org as the development server:
And then browse to http://mesh.pondersource.org:5800/ |
-> cs3org/ocm-test-suite#59 -> fixed |
Next: cs3org/reva#3365 (comment) -> done |
I could not reproduce this. If I set the source path wrong on purpose, with cs3org/reva#3369 I get:
so that improved error message should help debug whether it's an incorrect source path that is triggering the 404. Or maybe you have the iopUrl configured wrong and the 404 is to indicate a missing route on Reva. @mirekys Let's try to debug this on your server with the additional log messages I added, I'll ping you on Gitter! |
To debug this, we should:
|
We have the current stack as below:
run three instances from one owncloud source with
php -S
command.one Reva instance from Reva source code with this config:
one
MySQL
instance.when einstein shares a file with Marie,
Reva
receive the share and at the end when wants to call thesend
API, the logs show error 404.The text was updated successfully, but these errors were encountered: