Suspicious Login App Error after upgrade to NC31 from NC30

ℹ️ Support
, ,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 31.0.10
  • Operating system and version (e.g., Ubuntu 24.04):
    • Ubuntu 22.04 LTS
  • Web server and version (e.g, Apache 2.4.25):
    • Apache 2.4.52
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • nil
  • PHP version (e.g, 8.3):
    • 8.3.26
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • after upgrade to NC31 from NC30
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • command line updater
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no

Summary of the issue you are facing:

Error generated as below (ip address and username are masked). The messages “Error: Could not deserialize persisted model 157: Unrecognized message format.” did not appear in NC30. Our remote server was sync’ing files with NC via WebDAV. Huge amount of this error messages appeared.

Steps to replicate it (hint: details matter!):

  1. Upgrade to NC31 from NC30 with “Suspicious Login” App enabled.

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary

{“reqId”:“2qZPGoCbncn9h4NrRUJu”,“level”:3,“time”:“2025-11-14T04:23:55+00:00”,“remoteAddr”:“203.xx.xx.xx”,“user”:“kxxx”,“app”:“suspicious_login”,“method”:“PROPFIND”,“url”:“/remote.php/dav/files/kxxx/P678/1.%20Outgoing/As-Fitted%20Drawing/MVAC/M625-25%20-%20MVAC%20LMCP%20Panel%20Details%20%26%20Wiring%20Diagram%20%28Gas%20Purging%20Fan%29/%E6%96%B0%E5%A2%9E%E8%B3%87%E6%96%99%E5%A4%BE”,“message”:“Could not deserialize persisted model 157: Unrecognized message format.”,“userAgent”:“–”,“version”:“31.0.10.2”,“data”:{“app”:“suspicious_login”},“id”:“6916af0133d4d”}

1 Like
2

There is a longer issue on github where this happened in the past:

where they said that they switched the model at some point. This is long time ago, but with the regular cronjob this might go away quickly.
There is also a guide for manual training:

Before retraining, I’d check the commands, if there is a way to find a status or something of the current situation. Also if disabling/enabling the app helps that the checks are just enabled after the next cron-run (or it triggers a procedure when enabling).

1 Like