Hi everyone,
I’m experiencing an issue with my Nextcloud installation on a Raspberry Pi that I hope someone can help me resolve.
The issue:
For most of the user accounts in my Nextcloud instance, the display name and internal username are identical. However, my account is different—the internal username appears as an auto-generated UUID (for example, something like “e50d2368-5306-124d-929d-efc3ea171740”), while my display name is a friendly name. Notably, this account (with the random UUID) was the first user created after the admin account.
When I try to log in to an external tasks app (Planify, in my case), using my display name allows me to log in successfully, but no tasks or data are fetched. On the other hand, if I attempt to log in using the UUID (the actual internal username), the login fails entirely. My admin account (which has matching display name and username) works perfectly with external apps.
What I suspect:
It seems that the mismatch between the display name (used for human-friendly identification) and the actual internal username (the UUID) is causing the external app not to find the correct data. I’m wondering if this is expected behavior when an account is created with an auto-generated username or if I might have inadvertently enabled a setting that causes usernames to be auto-generated instead of manually defined.
Questions:
- Has anyone encountered this situation before?
- Is there a recommended way to ensure that the internal username matches the display name for new (or existing) users?
- Should I consider recreating the account, or is there a setting I can adjust to fix the mapping so that external apps can properly fetch my task data?
Any guidance or advice would be much appreciated!
Thanks in advance,