Recognize not working with Memories

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 30.0.4
  • Operating system and version (e.g., Ubuntu 24.04):
    • Yunohost
  • Web server and version (e.g, Apache 2.4.25):
    • nginx/1.22.1
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • replace me
  • PHP version (e.g, 8.3):
    • 8.2 and 8.3
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • replace me
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Yunohost / NC apps
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • I dont know
      la

Summary of the issue you are facing:

I have installed Memories and Recognize app in order to use the AI tagging features.

Everything in the admin panel pages for Memories and Recognize are green, except for few yellows like geolocation and skipped media file indexin, which seem unimportant.

The only thing from Recognize that has worked is that it has tagged a photo folder with very old pictures, like 10+ years old, with tags like people, cooking, tool, etc. Moving new pictures to that same folder will not get them tagged.

But after over 24 hours, nothing else has been tagged, such as dozens of recent pictrues that clearly have a car in them. Neither has been any “People” been recognized.

I’ve run the manual occ commands. Some of them work (work, as in no errors), suchs as

  • occ recognize:download-models
  • occ recognize:recrawl

Some of them don’t work, such as

  • occ recognize:reset-tags → Connection to LDAP server could not be established
  • occ recognize:classify → In Connection.php line 241: Connection to LDAP server could not be established

I already spent a few hours trying to fix this with ChatGPT with no luck.

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

  1. run the occ commands

Log entries

Nextcloud

Note: some of the configuration errors are related to when changed the “LDAP / AD username” setting, which made the web UI not work. That is fixed now, but the problem was the same before that.

https://pastebin.com/hBcffisZ

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

Idk know which log file to paste? There’s so many

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

https://pastebin.com/SV3sPhVb

Apps

The output of occ app:list (if possible).

List
  • app_api: 4.0.3
  • bruteforcesettings: 3.0.0
  • cloud_federation_api: 1.13.0
  • contacts: 6.1.1
  • dashboard: 7.10.0
  • dav: 1.31.1
  • federatedfilesharing: 1.20.0
  • federation: 1.20.0
  • files: 2.2.0
  • files_downloadlimit: 3.0.0
  • files_external: 1.22.0
  • files_pdfviewer: 3.0.0
  • files_reminders: 1.3.0
  • files_trashbin: 1.20.1
  • files_versions: 1.23.0
  • firstrunwizard: 3.0.0
  • logreader: 3.0.0
  • lookup_server_connector: 1.18.0
  • memories: 7.4.1
  • nextcloud_announcements: 2.0.0
  • notes: 4.11.0
  • notifications: 3.0.0
  • oauth2: 1.18.1
  • password_policy: 2.0.0
  • photos: 3.0.2
  • previewgenerator: 5.7.0
  • privacy: 2.0.0
  • provisioning_api: 1.20.0
  • recognize: 8.2.0
  • related_resources: 1.5.0
  • serverinfo: 2.0.0
  • settings: 1.13.0
  • support: 2.0.0
  • survey_client: 2.0.0
  • systemtags: 1.20.0
  • text: 4.1.0
  • theming: 2.5.0
  • twofactor_backupcodes: 1.19.0
  • user_ldap: 1.21.0
  • viewer: 3.0.0
  • weather_status: 1.10.0
  • webhook_listeners: 1.1.0-dev
  • workflow_ocr: 1.30.1
  • workflowengine: 2.12.0
    Disabled:
  • activity: 3.0.0 (installed 2.21.1)
  • admin_audit: 1.20.0
  • circles: 30.0.0 (installed 29.0.0-dev)
  • comments: 1.20.1 (installed 1.19.0)
  • contactsinteraction: 1.11.0 (installed 1.10.0)
  • encryption: 2.18.0
  • files_sharing: 1.22.0 (installed 1.22.0)
  • recommendations: 3.0.0 (installed 2.1.0)
  • sharebymail: 1.20.0 (installed 1.19.0)
  • suspicious_login: 8.0.0
  • twofactor_nextcloud_notification: 4.0.0
  • twofactor_totp: 12.0.0-dev
  • updatenotification: 1.20.0 (installed 1.19.1)
  • user_status: 1.10.0 (installed 1.9.0)

image

1 Like

This seems unrelated to recognize or memories. Your LDAP config seems to be broken, or your LDAP server is down.

Okay, but it’s still required for them to work? I don’t know how to fix it and everything I can find on google don’t seem to re related to my problem

It seems that the issue is not with the LDAP thing, because some new photos have been correctly tagged. These are photos taken with a phone and automatically uploaded to Nextcloud.

So it is partly working, but not tagging everything, even when the object is obvious, and it still has not regocnized any people.

Any ideas how to diagnose this further?

Yes, for recognize to work your nextcloud needs to work. A broken LDAP config is a pretty basic thing to be broken in a Nextcloud instance, a lot depends on the User backend.

I haven’t seen any configuration requirements for LDAP when installing Nextcloud, Memories or Recognize. What tutorial should I follow to get that fixed?

And why would tagging work for some photos but not others, if LDAP config was the issue? You’d think it either works or it doesn’t work.

Everything else in Nextcloud works as far as I have experienced (file uploads, syncing between devices etc).

1 Like

I don’t know the answers to these questions, sadly. I’m not an LDAP expert. Recognize doesn’t depend on LDAP, but if you get an LDAP error, I’d say you need LDAP help, not recognize help.