@ghisbar I cannot confirm your findings. The online help can be read without any problems with the latest Firefox browser. You should try to disable all kind of activated browser add-ins and check if the page can be displayed afterwards.

Hi @devvv4ever, thanks for the reply.

I have followed these steps and am using the App Password method.
When holding onto the Address Book for carddav and clicking “Properties” within the app, it shows the following Address URL: https://www.google.com/carddav/v1/principals/MYEMAIL/lists/default/
When I visit this URL in my browser, Google just shows a 404.

However, as mentioned, caldav is working as expected, so I think that my setup process was as expected.

Thanks

@rfc2822 Ah, okay. There are only couple of recurring events which are problematic for me right now, will manually update them.

Thanks for the help.

@j-ed - YES, you are correct. My phone was on my public (no password) wifi that has no access to the LAN that is password protected. It was designed to keep visitors out of my stuff.
And it worked - it kept me out of my stuff.
Thanks for seeing what should have been obvious to me!

Hi,
I ran into an issue when I migrated my Nextcloud reverse proxy from Apache2 (on my NAS) to ngnix on an opnsense firewall : my phone, and only it, could not synchronize contacts and calendar anymore. No issue with Nextcloud app, nor with contacts and calendar sync with Thunderbird or Windows 10 Mail app.

The error I got is a simple 403 response with a message telling I was banned and my mobile phone IP address was in the ban list on opnsense (in nginx module) but Nextcloud app still worked, it wasn’t banned.

So I looked at the user-agent DAVx⁵ was using to compare with le bot blocklist I read mentions of in one of the many sites, forum, faq… I read.

DAVx⁵ user-agent is :

The code responsible of the issue in opnsense is here :
https://github.com/opnsense/plugins/blob/b2d5d685e32968604feea055b8d6285211d4d0e1/www/nginx/src/opnsense/service/templates/OPNsense/Nginx/http.conf#L220

As you can see, okhttp in the user-agent string triggers the bot protection option in opnsense nginx implemetation.

The workaround is really simple : disable bot protection for my nextcloud instance and it is okay until I open the service from outside.
I think I can develop a quick and dirty fix in opnsense configuration but not sure the community would accept the patch.

I will also open an issue on opnsense side. If you can’t do anything about the user-agent sent by DAVx⁵, at least maybe this post will allow others to understand their issue. I did not find a lot of usefull information anywhere, maybe my keywords were too generic or my issue is really specific.

If you want more details or if I am not clear feel free to ask, I can reproduce the issue really quickly until I make my dirty fix to be able to access my Nextcloud instance from outside my network.

Works for me now. Tested it for telephone number and email fields.

OK, the problem is solved.
If I set the proxy in the Wifi connection, Android says that the connection is limited. As soon as you put the same proxy but in transparent mode (not set in Android, but filter correctely by the router when Android try to connect to outside), the connection is fully established and the synchronization is immediately done.
Sorry for the noise.
I would appreciate if one day, you may remove the needed support to Android sync…
Thanks a lot

Thanks for the update!

@jimmy Thanks for the update and good to hear that it now works for you! Maybe the thread can help others with the same problem.

@rfc2822 I executed a sync, failed, killed davx5 from the Android apps settings, started davx5, tried the sync again and failed with the same exception.

Marked as fixed (pending release) Thanks again for tracking it down.

@j-ed You were right! The issue was on the Nextcloud side - apparently some of the metadata of my contacts had been switched around. I fixed that and now my problem is solved. Thanks for the quick help.

@rfc2822
Thanks - I changed that setting and it is now working

@shunf4 If you don’t mind you can try to wipe the device and reset it to defaults. Maybe that helps - if not then Sony has introduced a serious problem into their Android.

What I remember from some support tickets: sometimes I have heard that it started to work users install the second tasks app as well. Then suddenly it starts to work also for the first one. Or did you try that already?

Because people are more often complaining about this in the last weeks we’ve created a new FAQ entry describing the problem:

[Google Contacts] Why are there “DAVx⁵ Address book” and “DAVx⁵” accounts?
https://www.davx5.com/faq/contacts/android-11-google-contacts

Hello
I have a Huawei P20 (Model : EML-L29).
I have paired the app Davx5 with my Provider with caldav

https://webdav.Provider/caldav

I have also successfully paired with the Provider on Linux/Ubuntu in Thunderbird using the add-ons “Provider for CalDav & CardDav” in conjunction with the add-on “Provider for Exchange Active Sync”.

There the pairing works perfectly. So the calendar works without problems with CalDav.

The entered as well as the complete synchronization can be synchronized on the homepage of the calendar for verification.

Since I also use Fruux (Under Evolution/Linux and Android, I can read entered appointments under Android also under Ubuntu, the synchronization works there as well.

Now yesterday I paired DAVx5 on my Androis with my calendar “https://webdav.provider/caldav”.

I did the pairing successfully with the two opensource calendars 1. “Simple Calendar Pro - Appointments & Reminders” and 2. “Etar -OpenSource Calendar” (F-droid).
So the calendar copy of the “mother app or control app” with the application apps works.

Yesterday I had seen that the entered appointments had also worked on all connected applications.

However, the appointments are now no longer synchronized on Android.
When I enter an appointment it is no longer visible. It also does not arrive under Thunderbird. There, however, the synchronization works.

I have read through the notes on Huawei and the corresponding settings in your app.
I’m not sure yet if I understood everything.

With the HuaweiP20 I have made the appropriate settings.
I turned off the automatic management, and manually enabled everything:
Auto Star:On
Secondary Start: ON
Run in background:ON

I have given all permissions to the app,I have made the battery settings also
If you want to let me know, I have seen that error codes can be read, these I can transfer into an editor and send you.

I have not done that yet:

EMUI 9+ devices
Classic battery optimization

Open Settings and search for Battery Optimization and access it. Touch the small inverted triangle next to Do Not Allow, touch All Apps, search and touch DAVx⁵ and select Do Not Allow.
PowerGenie

Translated with www.DeepL.com/Translator (free version)

@rfc2822 Hi, thanks a lot for the prompt and comprehensive reply! I’ll follow the https://github.com/nextcloud/deck/issues/15 for updates.