-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to create prosody users #109
Comments
FYI, |
I think you should not define the user twice. In your command prosodyctl --config /config/prosody.cfg.lua register myuser meet.jitsi mypassword You should also be able to use the environment variables. prosodyctl --config /config/prosody.cfg.lua register myuser $XMPP_DOMAIN mypassword FYI: I've added |
Doesn't work for me, gives me the same error. I didn't set anything special in the configfiles; certainly no hostname. The host setting above is the default. |
Figured it out after following prosody docs here https://prosody.im/doc/creating_accounts. Command is:
Command then asks for password. |
PR landed in |
hmmm this still gives issues : prosodyctl --config /config/prosody.cfg.lua adduser hugo@meet.xxx.yy |
with default XMPP host: prosodyctl --config /config/prosody.cfg.lua adduser hugo@meet.jitsi |
@hugokoopmans just restart the containers. Now check the prosody container id: That is it. |
I received the same error today.
Error Creating user failed |
Are you running that on docker? |
I am receiving a similar error when attempting to create a user in the Prosody container
|
I am taking the above action in accordance with the Docker self-hosting guide section regarding internal authentication. Any ideas as to why it wouldn't be working? |
Weird, do you see any errors in the container logs? Did you change the XMPP domain in your config? |
Thanks for the reply. Have not checked container logs. I'm unfamiliar with where to find them. How can I best do that? |
I have not changed the domain. |
You can do |
Thank you! Nothing shows up in the log when I attempt the user creation. The last entries are all from my most recent test conference a few days ago. |
Still confirming that all did indeed work, but it would appear that modifying the above command to the following avoids the error. |
Hum, that's odd. Can you share the generated prosody config files? |
Yes I can. I have just been testing to see if after the updated 'auth.meet.jitsi' version of the command works, however it doesn't seem to recognize the user/password combo. Will share the current logs below. |
That would suggest auth is not actually enabled for the main domain. |
|
oh god, sorry about the formatting, will attempt to improve |
That doesn't help much. What env vars did you set? Can you get the jitsi-meet.cf.lua file off the container? |
the env vars for authentication that I have configured are: fetching that file now |
admins = {
} unlimited_jids = { plugin_paths = { "/prosody-plugins/", "/prosody-plugins-custom" } muc_mapper_domain_base = "meet.jitsi"; http_default_host = "meet.jitsi" consider_bosh_secure = true; smacks_max_unacked_stanzas = 5; VirtualHost "meet.jitsi"
VirtualHost "guest.meet.jitsi"
VirtualHost "auth.meet.jitsi" VirtualHost "recorder.meet.jitsi" Component "internal-muc.meet.jitsi" "muc" Component "muc.meet.jitsi" "muc"
Component "focus.meet.jitsi" "client_proxy" Component "speakerstats.meet.jitsi" "speakerstats_component" Component "conferenceduration.meet.jitsi" "conference_duration_component" Component "endconference.meet.jitsi" "end_conference" Component "avmoderation.meet.jitsi" "av_moderation_component" Component "lobby.meet.jitsi" "muc" Component "breakout.meet.jitsi" "muc" Component "metadata.meet.jitsi" "room_metadata_component" |
Very odd, your main domain does have auth on! |
Just took a look into /config/data/auth%2emeet%2ejitsi/accounts in the container, and it would appear that both the transcriber and the admin account I created have .dat files there, alongside jibri.dat, focus.dat, etc. |
Perhaps the above because the accounts were not created for the main domain but for the auth.meet.jitsi domain? |
That's correct yes, they don't match the domain. |
Note that when copying, except for the spaces in the text |
Following up on this issue. If the auth issue is due to users not being registered on the meet.jitsi domain, and attempting to register users to the meet.jitsi domain always throws the "Error: Creating user failed" error, then we are stuck. I'm in conversation with Prosody support about why the error could be occurring. Any further insight here would also be welcome. Thanks all |
User creation has just worked for me. I followed suggestions in this thread to remove and cleanly reinstall all containers and the config directory |
I'd like to use auth. However, I fail to create prosody users:
Any ideas?
PS: the docs are wrong, I needed
docker exec -it jitsi_prosody_1 /bin/bash
to get into the containerThe text was updated successfully, but these errors were encountered: