Cannot continue with account creation
I'm stuck on the account creation page 😦 After entering a username and a password, and clicking on Continue, the spinner just keeps spinning. Any ideas on what could be done to resolve this?
Solution:Jump to solution
The problem was solved by moving this docker container to NFS, where permissions are handled way easier. F*** SMB
23 Replies
Please post your log
Did you try restarting the app once?
Yes
Are you running from source?
not sure what that means. Could you please elaborate?
BTW, here's what I have in the browser console
Here's a more detailed version
{
"meta": {
"response": {},
"responseJSON": [
{
"error": {
"json": {
"message": "database is locked",
"code": -32603,
"data": {
"code": "INTERNAL_SERVER_ERROR",
"httpStatus": 500,
"path": "user.createOwnerAccount",
"zodError": null
}
}
}
}
]
},
"shape": {
"message": "database is locked",
"code": -32603,
"data": {
"code": "INTERNAL_SERVER_ERROR",
"httpStatus": 500,
"path": "user.createOwnerAccount",
"zodError": null
}
},
"data": {
"code": "INTERNAL_SERVER_ERROR",
"httpStatus": 500,
"path": "user.createOwnerAccount",
"zodError": null
},
"name": "TRPCClientError"
}
🚀 Installation | Homarr documentation
We provide multiple installation methods. Are you a newbie to Docker? We recommend Docker Compose for beginners.
Since the above logs state that the database is locked, I think it's important to mention that previously I had an issue mentioned here https://discord.com/channels/972958686051962910/1172826100209025135.
As a solution, I copied the database shared in the aforementioned post and the installation issue was resolved.
Discord
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
What are the permissions on the file? Who's the owner? What user is docker running as?
This is the output of "ls -l db.sqlite" from debian: -rwxr-xr-x 1 xxx xxx 0 Jan 10 13:29 db.sqlite
This is the output of "ls -l db.sqlite" from TrueNAS: -rwxrwxrwx 1 xxx root 0 Jan 10 11:29 db.sqlite
The way everything's organized is there is a TrueNAS-created SMB network share where all my docker containers are stored. I am connected to it via Debian and MacOS. Is use Debian for all my docker stuff. And I used MacOS to download and replace the 0 byte db.sqlite. What's interesting is that from MacOS it shows that a group everyone has no access and I can't update it from MacOS. I also tried to chmod via Debian and the process just froze and couldn't finish executing, so I had to hard reset the OS. From TrueNAS the chmod command executed without any problem but that didn't help with the posted above problem.
I'm not really sure which OS shows the correct permissions. The owner is also different depending on the OS.
I have a feeling that this and https://discord.com/channels/972958686051962910/1172826100209025135 are related in my case. The similarity in both cases is that somehow the system can't write into the file.
If your system cannot chmod, there might be something seriously wrong with it
Please check if the user can write / read
@Tag can maybe also help with permission issues. But we generally don't support any custom solutions, like SMB shared or filesystems over network (it's really up to you to get that running). Ensure that you also don't run Homarr as a custom user, as this may cause problems with the container. Running as root / privileged is recommended, although it's not the most secure option. It's a know bug and will hopefully be resolved in future versions so you can use custom users.
Chmod 777 the file and folder from debian, see id that help
It's not recommended since it makes the file readable and writable by anyone that has access to the network, but at least it would tell us if permissions are the only problem
chmod 777 a file and a folder from Debian (both user and root) didn't change the permissions, unfortunately 😦
I created a new dummy file in the same directory from Debian. Then I tried to chmod, but that didn't work either. My brain can't spit anything else except WTF! 😄
Sudo chmod?
Sudo doesn't help either
Were there any other users with a similar issue?
You can try searching the discord on answeroverflow:
https://www.answeroverflow.com/c/972958686051962910
Homarr Community - Answer Overflow
Questions and answers related to Homarr
Here's what I've found out so far. The SMB share is mounted as a CIFS and Unix permissions are ignored for CIFS (in fact, once you create a dataset as a Windows dataset in TrueNAS, you can't even use the chmod command on it anymore). I have to use Windows ACLs instead of Unix permissions for Windows.
Digging further...
Moving forward, while it's not too late, I'll probably ditch SMB/CIFS altogether and just switch to NFS.
Solution
The problem was solved by moving this docker container to NFS, where permissions are handled way easier. F*** SMB
Aha interesting. I’m curious why you guys @Tag @Manicraft1001 didn’t suggest to simply remove the mountpoint for the db, since it will be inside of a docker volume which will have wr+ access by default and should’ve also fixed the issue 😉
(and yes it’s persisted even if you update the container, you don’t lose users)
I personally have it mounted to an SMB share too, working just fine.
I think I made it the same when I helped Mani set up his as well.
Do you have a resource about setting up a nfs truenas share. Ive run into the same issues but I cant get nfs permissions working correctly. Every video ive watched just does smb. I can mount the nfs share but i get a permission denied when i try to cd to the directory. I set the ACL in Truenas so that everyone in the group has full control but its not working