Hi Boris & team,
it seems like I cannot reuse very old (I was to write “ancient” ) user names (error msg: There were issues creating the account: The account identifier (Username) is invalid.) even if they are not used anymore and - quite funny! - I’m using a freshly flashed system with just Nextcloud at the moment. These user names are NOT present as folder names under /opt/disk/external/nextcloud.
I think that there are traces within my externl disk (/data) that prevents me from reusing those names. Could you kindly help me to understand what data I need to clean to be able to go ahead?
I seize the opportunity to ask you an advice: the problem I’m facing rises from the idea of using the application USERS instead of letting the apps to manage them or, much worst, to use the Admin credentials in those apps where I have a single user (typically myself). Do you think it is still a good idea? What about reflashing a system and restoring users and apps from backup with this “new” approach? Thanks
In my opinion, correct me if I’m wrong, the user “Sandroski” is still present somewhere in the system and due to that I’m prevented from creating it. Hints:
within Nexctloud folder it is not there anymore. I am sending the logs, immmediately after a couple of attempts;
I can create new users if I use names that have never been used in the past
hello Boris,
today I wanted to retry everything so I reflashed the system once again.
Now I can recreate user also reusing old user names BUT…there is a difference: I have changed the domain name ([…].syncloud.it). I don’t know the architecture but according to yesterday’s and today’s experience here it is what I have learned and I’m sure about:
I cannot understand what happens. Some users can be created some other can’t. I cannot find a beaviour that I can repeat. For the moment neglect the entire thread. What I’m sure is that I cannot create anymore an old user called “Sandroski”. I have been able to recreate others users. Frankly speaking I cannot figure out what is the rationale behind it.
Hi I see the issue, latest update broke LDAP integration, I am adding more automated tests and reusing what latest photoprism now supports, I will come back.