User Creation Failing
-
Hello All,
I'm excited to see that Linkwarden was added as a new app! I have the app installed, but there seems to be a few issues when creating a new user, either via the admin page or trying to register. This does seem to only be an issue when the app is setup with leaving the user management to the app "Login with dedicated account" vs. SSO via Cloudron.I'm seeing the following errors in the dev console, when trying to submit the form.
admin-e6140dc4287cb378.js:1 POST https://app.cloudron.tld/api/v1/users 400 (Bad Request)
admin-e6140dc4287cb378.js:1 Uncaught (in promise) Error: Please fill out all the fields. at Object.mutationFn (admin-e6140dc4287cb378.js:1:5312)
I wasn't sure if this was an upstream issue or package issue. Any thoughts or any further information needed on this?
Thank you!
Edit: Updated authentication use-case context
-
Actually, come to find out I was able to dig this up from their GitHub.
https://github.com/linkwarden/linkwarden/issues/225#issuecomment-1762781340
-
-
@nebulon I just gave this another shot and it seems if Cloudron User Management is enabled, I'm able to login without issues. Although, I'm still not able to delete the admin user or change the admin in the
env
file toNEXT_PUBLIC_ADMIN=1
.If I create the app without Cloudron User Management, I'm still facing the same error.
-
Edit: Actually, it looks like the admin account reverts, so the below doesn't seem to work. Also logging into the account and trying the "Delete" account, doesn't seem to work either. If you login to the account, click delete account, it logs you out, but the account remains.
I have a bit more info on this. So the workaround is to complete the change in the
env
file and then manually go tohttps://{appurl}/admin
after an app restart, delete the admin user, and you should be good. To note, once you make the change to theenv
, the "Server Administration" option in the menu will not show up, but going to the admin url will work. -
I'm actually not quite sure, I would have to look at the package. I had found another related GitHub issue upstream.
-