@devvv4ever the notification is sent by opentasks, and yes, the notification is for a task that is past due, I am usually setting due for tasks to remind me at that time, the notification pops up on due date/time which is fine, but then when I do not clear that notification, it pops up again on every sync, like it was a new notification, but it isn’t, it’s still the same one which has already been there for some time.
no WiFi sync only 4G works
-
Hello,
I bought the DAVx5 long time ago (for Android) and it always worked with my Nextcloud on Pi.
I was very happy w/ this nice little tool.But since some few weeks I cannot sync any more. My pad w/ WiFi only can not at all and my phone (Nokia 8 w/ Android 9) only when I disable WiFi connection (-> over mobile connection 4G).
I deleted account in DAVx and configured new, but it cannot find services. Also I playes w/ WiFi only sync option in DAVx but it does not help.
Any ideas?
PS: Outlook w/ CalDav plugin works as well. -
Hello,
Sounds like a connectivity/internal network problem of your WiFi. Can you please post
- an explanation what “cannot sync anymore” means – is there an error message, does it fail silently? etc.
- whether it works when you force synchronization while you’re on WiFi
- debug info
- verbose logs when you force synchronization
- details of the account creation error?
Thanks!
-
deleted.
Proxy was enabled. -
You have activated a proxy setting in the davx5 app settings. Please deactivate it and try again. Does that help?
-
correct, sorry I was playing w/ different settings.
Now proxy is off.Well it is not a device issue, I see this on 1 tablet and on 2 phones.
I attache some files.
davx5-log.txt
-
Maybe your router or firewall changes the caldav or carddav requests from DAVx5 so that the server can’t process it anymore… Thats the only thing I could imagine.
-
Your server sent a 400 Bad Request response, but the request looks fine. Please have a look at your server logs, maybe you can find the reason there. Which server/version are you using?
-
Thanks @devvv4ever for your hint - it did it !
I really had to add a exception in the router (AVM Fritzbox), as descripted below:
https://en.avm.de/service/fritzbox/fritzbox-7581/knowledge-base/publication/show/3423_FRITZ-Box-reports-400-Bad-Request-when-accessed-with-own-domain-name-or-CNAME/Here an screenshot for other affected people:
I stuck there for weeks, router update & android app not working anymore what a pity.
-
@bingo Thanks for the update!