[SOLVED] hacking attempt origin:Z-push not working anymore

Hi there,

since yesterday, z-push does not working anymore.
i have not changed everyting, so something goes wrong?
MIAB 0.44, ubuntu 18.04 LTS,no modifications, all updates installed

z-push errorlog:

...returned the http status code 405.
03/05/2020 08:58:51 [23741] [ERROR] [guenther@DOMAIN] BackendCardDAV- 
>GetGALSearchResults : Error in search query. Search aborted
03/05/2020 09:35:57 [30859] [ERROR] [claudia@DOMAIN] BackendCardDAV- 
>GetGALSearchResults : Error in search Woops, something's gone wrong! The CardDAV 
server returned the http status code 405.
03/05/2020 09:35:57 [30859] [ERROR] [claudia@DOMAINt] BackendCardDAV- 
>GetGALSearchResults : Error in search query. Search aborted
03/05/2020 14:22:17 [30867] [ERROR] [office@DOMAIN WBXMLDecoder- 
>getElementEndTag(): could not read end tag in '/usr/local/lib/z- 
push/lib/request/resolverecipients.php:44'. Please enable the LOGLEVEL_WBXML and send 
the log to the Z-Push dev team.
03/05/2020 14:22:17 [30867] [FATAL] [office@DOMAINt] WBXMLException: Unknown error 
in ResolveRecipients->Handle() - code: 0 - file: /usr/local/lib/z- 
push/lib/request/requestprocessor.php:117
03/05/2020 14:22:17 [30867] [FATAL] [office@DOMAIN] WBXML 10K debug data: 
AwFqAAAKRVADb2ZmaWNlQHJvb21vbHV0aW9uLmF0AAFPWl0DMQABAQEB
03/05/2020 14:22:17 [30867] [FATAL] [office@DOMAIN] Exception: (WBXMLException) - 
Unknown error in ResolveRecipients->Handle()
03/05/2020 14:22:17 [30867] [FATAL] [office@DOMAIN] Request could not be processed 
correctly due to a WBXMLException. Please report this including the 'WBXML debug data' logged. Be aware that the debug data could contain confidential information.

done sudo mailinabox and rebooted, but nothing changing.

please help

SOLVED!

it turns out, someone tried to hack? my MiaB-Server with the OpenVAS-VT tool via WebDAV/Roundcube.
It was not a problem, but the Nextcloud bruteforce-prevention blocked 127.0.0.1.
so it was clear, that MiaB shows something weird behaviour.
deleting 127.0.0.1 from Nextcloud-DB table oc_bruteforce_attempts solved my issue.

dammed!