Closed fuzunspm closed 2 years ago
KeePassium does not store your Nextcloud credentials and does not send network requests to your server. The app delegates synchronization to the original cloud provider's app. (Or, more precisely, its File Provider module which handles Nextcloud integration with the standard iOS Files app.)
So this is purely a Nextcloud issue that has nothing to do with KeePassium. You can try to replicate the issue by opening Nextcloud-stored PDF files in the standard Files app, and editing them using Markup feature (still in the Files PDF preview). Requests received by your server in this scenario should be very similar to KeePassium's workflow.
I have 3 others apps that use Nextcloud storage and they don't have this problem.
I assume these apps communicate with your server directly, not via the Files/Nextcloud integration.
Is there any follow up issue in the Nextcloud app? I'm facing the same issue
@ann0see , I don't think so, unless one was created independently.
By the way, since my previous response here KeePassium added support for direct WebDAV connections. It works with Nextcloud storage without relying on Nextcloud app, so this might be the quickest solution.
Thank you for your answer. I've updated the regular expression for the Nextcloud fail2ban jail. Let's wait and see.
Description I have fail2ban configured for Nextcloud authentication and Keepassium keeps making failed authentication attempts and gets IP blocked
Environment:
Here is the Nextcloud logs triggered by Keepassium. I have 3 others apps that use Nextcloud storage and they don't have this problem. I tried to re-login/re-install both apps but it didn't fix the problem