Akonadi lock nextcloud

Hi,
Since I had started Akonadi, there are too much attempt to connect to my nextcloud which result on brute force protection trigger from the server. So, is there a way to temper these connections from akonadi, and, by the way understand why akonadi do that (tehre is only Korganizer at startup) ?

Furthermore, the desktop double time to open.

Thanks foi help.

Hi,

in order to sync calendars, there are a few requests that must happen every time.

Could you maybe try to decrease the refresh/sync interval of the calendar?

Also, how is your Brute Force protection configured? I can try to set it up on my Nextcloud and see if I can reproduce it.

Thx.
Well, about reducing the rsync yes, good point but from the clock in the tray I can’t (?). I guess it takes information from korganizer, but…

Korganizer is not connected apparently. this is another problem : it says in configuration/Agendas/Nextcloud ready, but doesn’t show any calandar from the server. So let’s forget that one.

My brute force conf : I did not do anything special it is the Nextcloud default
Have no idea how to configure it.

Complement : I just started akonadi and no problem. So, may be the default occur only when I open the plasme session. I will check it later, cause now the computer is making backup for a while.

So, finally I resolved the problem with korganizer and its connection to the cloud, and the problem vanished. I guess it happened because Akonadi was trying many times to get the connection in vain.

But I still don’t understand what was the actual problem and how it was solved. Could you please clarify it?

Ok I’ll try. Sorry for not be clear.

So, I was using Plasma without akonadi. Fine. Then I decided to use korganizer, i.e. to set up as well akonadi.
Here started the problem : nextcloud always disabling my user and sending a message about brute force. Obviously, there was a link in between one and the other.
What I did is trying to get back : no use of korganizer, and disabling akonadi. did not work, the problem persist. Akonadi started every time I open a session. And everytime the same problem with the cloud.

so finally I setup and configure properly korganizer, because I realised it was not set up properly regarding connection to the cloud. And things are done.

… or almost : the session is significantly slower to open. And would like to fond out the logs of akonadi to see what is done, but I don’t find them.

But what is the proper configuration of Korganizer? I just added caldav and carddav accounts, and it worked without issues for half a year. And for the last 2 days I have issue with “too many requests” (brute force protection). Should I remove them and add again?

I can’t recall when the client was updated (current version is 3.11), but that might be the root of the problem. I turned on VPN, and now it’s ok, but I’ll follow up behavior

But I also use floccus FF add-on for bookmark sync, and it also has some issues last few days. And that one doesn’t depend on akonadi or korganizer, so I’m quite confused. Still have to check how’s everything working on other machine (also KDE, but everything else is different)

Hi,
Sorry, I wasn’t able to us computer for a while.
Well, so, things are not clear.
I had just updated the whole fedora, plasma etc and i do not use anymore Korganizer. But I still have such problem, wihich is, I guess, coming from the following sequence…
1- open a session
2 - a pop up window apear to ask for general password, but vanish instantly because other windows open
3- thunderbird starts, firefox end dolphin - all of it may access to nextcloud in some way
4 - I finally set the password in the first window
But already brute force settings had disabled my account in my cloud.

On the laptop, the same sequence doesn’t lead to that problem. So I have to find trace of something somewhere to know what start communicating with my nextcloud instance and when, and identify what is locking what.

No idea how to do that, probably from the logs of the cloud itself.

1 Like

Yes, I notice similar behavior when I don’t enter KDE Vault password immediately

So that is a problem.
Another one, is that after entering the password and everything ok, then, you can re-enabled your account on nextcloud server, and, for example open dolphin with a dav … your nextcloud account will be disable again.

So, what I did is disabling akonadi… not a good idea. Looking for how to control akonady in some way… it is more like a blak box than anything else and looks like “une usine à gas” as we say here.
For instance, the best I found is to switch to xfce.

I have another computer, laptop just set up with plasma. No problem at all.

So, I come back on the first question : which log can I read to compare both machines and identify the source of the problem on the first machine ?

Give up ! Did not find the problem. I used XFCE.