Error with share extension app 2.25.0

tdbsoft commented 4 years ago

Expected behaviour

Allow saving, send of data to NextCloud server.

Actual behaviour

Goes slow then bugs with error windows (see below)

Steps to reproduce

open photos on iPad click share icon select NextCloud icon select folder to save on server

iOS version

12.4.3

App version

2.25.0

Server configuration

NC 16.0.4 or NC 15.0.11 Operating system: Linux Centos Web server:

Database:

PHP version: 7.1.32 Nextcloud version: (see Nextcloud admin page) 16.0.4

We have 2 servers running NextCloud 15 until recently all working well, 7 days ago we believe that the NextCloud App on the iPad was updated to version 2.25.0 after that these errors started happening. We have tried updating the NextCloud Server to version 16.0.4 but that had no effect as the error is still happening.

Next we tried to isolate issue on our second NextCloud server which also was running NC 15.0.11 and was working correctly with the IOS iPad App version 2.24.x but after updating the IOS NextCloud App to version 2.25.0 the same error start to occurred.

Looking at the log on the server it is reporting errors like this {"reqId":"ifbinmpC53W4aukKT2Ow","level":2,"time":"2019-11-27T14:02:30+00:00","remoteAddr":"192.168.50.104","user":"--","app":"core","method":"PROPFIND","url":"\/nextcloud\/remote.php\/webdav\/ipad\/More\/Fred\/Test\/2019-11-27%2018-06-12-1.xlsx\/","message":"Login failed: '573dddf4-3ca0-1039-8e14-5bc531870439' (Remote IP: '192.168.50.104')","userAgent":"Mozilla\/5.0 (iOS) Nextcloud-iOS\/2.25.0","version":"16.0.4.1"} {"reqId":"pIuHqRGxweP7r4weZQvR","level":2,"time":"2019-11-27T14:10:11+00:00","remoteAddr":"192.168.50.104","user":"--","app":"core","method":"REPORT","url":"\/nextcloud\/remote.php\/dav\/files\/573dddf4-3ca0-1039-8e14-5bc531870439","message":"Login failed: '573dddf4-3ca0-1039-8e14-5bc531870439' (Remote IP: '192.168.50.104')","userAgent":"Mozilla\/5.0 (iOS) Nextcloud-iOS\/2.25.0","version":"16.0.4.1"}

We have search on line and have not found any answers.

bh11 commented 4 years ago

Similar problem here, Nextcloud server 16.0.6.1, iOS 13.2.3.

This might be related to LDAP generated users whose user names are of the form 573dddf4-3ca0-1039-8e14-5bc531870439 while display names are the user names coming from LDAP.

Similarly, a GET request (from within the Nextcloud app) using the display name works, but a PUT request (sharing a file with the Files app and trying to save to the Nextcloud root dir) with the user name for authentification doesn't (despite the 201 result code, the file never gets uploaded).

From nextcloud.log:

192.168.0.1 - john.doe [28/Nov/2019:17:21:23 +0100] "GET /nextcloud/remote.php/webdav/example.txt HTTP/1.1" 200 366401 "-" "Mozilla/5.0 (iOS) Nextcloud-iOS/2.25.0"

192.168.0.1 - 071af7f2-e6ad-1037-8e64-af79d243c530 [28/Nov/2019:17:21:32 +0100] "PUT /nextcloud/remote.php/webdav/example.txt HTTP/1.1" 201 3942 "-" "Mozilla/5.0 (iOS) Nextcloud-iOS/2.25.0"

bcutter commented 4 years ago

Same for me. Very annoying. Nothing with LDAP used, might be a networking/SSL validation issue. OR (just an idea!) too many wrong/failed authentication requests triggering the integrated ban protection. Might be tested by getting another IP adress (e. g. on mobile data carrier).

bh11 commented 4 years ago

@bcutter Do you see this problem for local users as well? As far as my installation is concerned, this only seems to affect LDAP users (maybe SSO as well?)

bcutter commented 4 years ago

Only local users, so I don’t count for the LDAP thing.

shotzi commented 4 years ago

This concerns not only the IPad its a problem with all ios devices. It's no problem to share a object from inside the nextcloud with another app on the same device, but as soon as you do it the other way around starting from another app like the foto gallery to send it to nextcloud you end up with the error message that's shown above. It's even worse because we use LDAP and set a limit to max bad password attempts the user is blocking his account. Seems like the error causes multi times wrong logins for this user. As a result he is blocked in other systems as well.

In a workflow where you depend on ipads for example to store your pdf document in NC and share this with your pdf app to fill in the information and then send it back to NC. You are stuck now.

Server version 17.0 Client 2.25

Any idea when this is fixed, or how we could set up a workaround?

bjo81 commented 4 years ago

This issue also appears in a setup with 17.0.1 connected to an AD. Users login via their usual AD username, the log is full of failed logins from UUIDs as already stated by @bh11. Uploading files within the app works but if the data is shared from another app into the NC app, the above issue occurs.

bh11 commented 4 years ago

The issue is still present in the 2.25.1 beta released 2019-12-05, unfortunately.

shotzi commented 4 years ago

Jep still not functional even with the 2.25.1 released version in the appstore. That's a real problem for people that use this function in their workflow.

shotzi commented 4 years ago

any news regarding this bug?

marinofaggiana commented 4 years ago

please test with TestFlight V 2.25.3 (3)

bh11 commented 4 years ago

Here, sharing works again with TestFlight V 2.25.3 (3).

hoferbeck commented 4 years ago

Hello!

I have tired to install 2.25.3(6) but i get the same error like the screenshot above

Should i set some settings?

I use a user with two factor but the IPad has an App password

I use nextcloud 17.0.2 in a docker container on an unraid system the ipad is the ipad 5.gen but i also have the issue with my iphone 5s

BR

bcutter commented 4 years ago

I don’t think this is closed: still seeing this issue with iOS app version 2.25.3.6 on server version 17.0.2.1.

bcutter commented 4 years ago

To be more precise: this is what happens in nextcloud.log when trying to upload a photo to nextcloud using the share extension:

{"reqId":"XXXXXXXXXXXXXXXXXXXX","level":1,"time":"2019-12-27T20:20:54+01:00","remoteAddr":"192.168.178.36","user":"--","app":"core","method":"PROPFIND","url":"\/remote.php\/webdav\/","message":"Bruteforce attempt from \"192.168.178.36\" detected for action \"login\".","userAgent":"Mozilla\/5.0 (iOS) Nextcloud-iOS\/2.25.3","version":"17.0.2.1"}

Then bruteforce protection kicks in and the error message (similiar to the one from the thread opener) is presented.

hoferbeck commented 4 years ago

I can confirm that discovery from @bcutter

I also can add when you add the client to the brute force expetions list as a workaorund you get a Login failed message in the log file:

{"reqId":"xxxxxxxxxxxxxxxxx","level":2,"time":"2019-12-27T10:23:35+00:00","remoteAddr":"192.168.1.25","user":"--","app":"core","method":"PROPFIND","url":"\/remote.php\/webdav\/","message":"Login failed: 'xxxx' (Remote IP: '192.168.1.25')","userAgent":"Mozilla\/5.0 (iOS) Nextcloud-iOS\/2.25.3","version":"17.0.2.1"}

bcutter commented 4 years ago

Why the freaking hell is this still closed? The bug is NOT fixed!

This has really a huge impact, e. g. using Files Integration on iOS data can not be saved to Nextcloud (workflow: app doing write changes —> Files Integration —> Nextcloud app).

Log and prove are here, what you waiting for? REOPEN this issue please!

bcutter commented 4 years ago

Re-open this issue! IT - IS - NOT - FIXED!

tdbsoft commented 4 years ago

I second bcutter statement Re-open this issue! IT - IS - NOT - FIXED! At the moment Nextcloud is virtually unusable due to this issue.

bcutter commented 4 years ago

Go to https://github.com/nextcloud/ios/issues/1113

bcutter commented 4 years ago

Since app version 2.25.8 this error (code 401) seems to be fixed. Can others confirm?

tdbsoft commented 4 years ago

Hi BCutter,

Yes seems to be working but need additional testing.

Cheers,

Trevor

TDB SOFTWARE

Website: www.tdb.com.au http://www.tdb.com.au/ Email: trevor@tdb.com.au mailto:trevor@tdb.com.au

Voice: (08) 9390 7457 Mobile: 0407 424 924 Fax: (08) 9467 6223

From: bcutter notifications@github.com Sent: Tuesday, 18 February 2020 3:37 AM To: nextcloud/ios ios@noreply.github.com Cc: tdbsoft trevor@tdb.com.au; Author author@noreply.github.com Subject: Re: [nextcloud/ios] Error with share extension app 2.25.0 (#1022)

Since app version 2.25.8 this error (code 401) seems to be fixed. Can others confirm?

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nextcloud/ios/issues/1022?email_source=notifications&ema il_token=AN4QHIA3V32IJVQARZGGU73RDLRO7A5CNFSM4JSH3OOKYY3PNVWWK3TUL52HS4DFVRE XG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL7O5YQ#issuecomment-587132642 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4QHIBLSGXVZCJPQ7YCJHDRD LRO7ANCNFSM4JSH3OOA . https://github.com/notifications/beacon/AN4QHIBTLPHXTMNFTZKMTETRDLRO7A5CNFS M4JSH3OOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL7O5YQ .gif

jospoortvliet commented 4 years ago

Dear @bcutter and others please keep in mind when replying that we're not working for you for free. Ref this excellent blogpost on the issue: https://berthub.eu/articles/posts/anonymous-help/

If your business needs Nextcloud to work reliably, get a support subscription, that is what gives you priority. Not yelling at us on github, that is actually a motivation for our people to NOT provide any solution until people calm down.

bcutter commented 4 years ago

Got it. But a sign of life („we‘re looking into it, please take a seat“) would sometimes be enough. No corporate users here (speaking for myself). And there are bugs I‘d pay some €/$ to be fixed but that kind of service reward system doesn’t exist as far as I know.

nextcloud / ios