Daniel Bölts

Hi @TuggyNE, * Forgetting the auth token: maybe you are right and this should be fixed. There are others reported issues relating to this. * Privileged ports: I don't use...

* For Mega the request #124 exists. * GMX is WebDav-Compatible: no provider is required here, it's supported in KeePass out of the box - details see #20.

Yandex-SDK: https://github.com/yandex-disk/yandex-disk-sdk-csharp

Hi @mzarglis , could you please start KeePass with Parameter "-debug". The error message should then be slightly different with more details or a Temp-Filename with details. Could you please...

I will take a Look at it. On So., 24. Sep. 2017, 09:16 slingshot27 wrote: > Will this issue been fixed? > > — > You are receiving this because...

I'm sorry, I'm still very busy. So I haven't had any time to dive into this :-( slingshot27 schrieb am Fr., 13. Okt. 2017 um 11:07 Uhr: > Hi Kyrodan...

I will keep an eye on it.

KeePass 2.37 is not the source problem as it seems this issue also hits other KeePass versions.

I recently released v1.5.1. Could you please try to reproduce your issue with this version (an KeePass 2.40)?

Which Windows Version are you using? Do you have any user or firewall restrictions? Could you try to start KeePass with admin/elevated permissions? The ports are only required for authentication....