Issues with verifying Jitsi users #24
Comments
|
Good afternoon I have exactly the same problem. Did you manage to find a solution? |
I encountered the same problem. I got http/404 error in journalctl for request to http://matrix-synapse:8008/_synapse/admin/v1/rooms/!YSiInWMBvgnICjPOJB:server.com/members. I found that matrix-user-verification-service was making requests to http://matrix-traefik:8008, but Traefik was returning a 404 error. To fix this, I set the matrix_user_verification_service_uvs_homeserver_url to http://matrix-synapse:8008 and ran the following command: After this, everything worked correctly. I believe the issue is that Traefik needs to be properly configured to balance the Synapse 8008 port and handle the locations correctly. |
I'd like to start by thanking the devs (and everyone contributing) for creating and sharing such a great tool.
Please note I've used https://github.com/spantaleev/matrix-docker-ansible-deploy to set this up.
Unsure wether this issue would fit better in this repo than the other one. Since prosody-mod-auth-matrix-user-verification is the heavy lifter in my use case, I'm hoping I'm in the right location.
Original issue: spantaleev/matrix-docker-ansible-deploy#3332
Jitsi Integration with Matrix/Element Failing with Authentication Errors
I am using this repo to install Matrix, Element, and Jitsi. My goal is to have Jitsi authenticate with Matrix using auth method
Matrixand use OpenID auth provided by Keycloak on Matrix. However, I am encountering issues where Jitsi fails to authenticate users, leading to errors both when using the native video button in Element and when adding a Jitsi widget via Dimension. Here are the detailed steps, configurations, logs, and troubleshooting steps taken.I was hoping someone could point me in the right direction to solve this.
Steps to Reproduce
Installation and Configuration:
vars.ymlas needed.just register-user admin password yes, obtained an access token for the admin user and used that for theaccess_tokenvariable invars.yml. Then enabled UVS and Dimension and let them use the access token invars.yml:Jitsi Configuration:
jitsi_enable_authis set tofalsethrough both the native video button in Element and the Jitsi widget via Dimension. Afterward when set totruethe problems begin.Authentication and Integration:
jitsi.domainand not tomeet.element.ioormeet.jit.si. For both video icon and widget initiation of a jitsi meet.https://jitsi.example.com/{{Your conference id}}?jwt={{the jwt authentication token}}.Attempt to Start a Jitsi Call:
Expected Behavior
Jitsi should authenticate with Matrix, allowing users to start and join video calls seamlessly and promote a user to moderator if applicable.
Actual Behavior
Using the Native Video Button in Element:
nbfvalue. Invalidexpvalue."Using the Jitsi Widget via Dimension:
adminuser created earlier and thetestusers from my keycloak server.Logs and Configuration
(Redacted my actual domain with either *.domain or *.example.com)
Logs for
matrix-jitsi-jvb.serviceLogs for
matrix-jitsi-jicofo.serviceLogs for
matrix-jitsi-web.serviceLogs for
matrix-jitsi-prosody.serviceLogs for
matrix-user-verification-service.serviceVars.yml Configuration:
requirements.yml versions:
Troubleshooting Steps Taken
Manual User Registration in Prosody:
docker exec matrix-jitsi-prosody prosodyctl --config /config/prosody.cfg.lua register testuser meet.jitsi testpassResult:
The given hostname does not exist in the configConnecting to the Matrix User Verification Service:
docker exec matrix-jitsi-prosody wget http://matrix-user-verification-service:3000Result:
404 Not FoundUVS
When exposing the port on 3000 via:
I execute this with a valid access token:
It returns:
{}This also has the same result when I execute it within the prosody container after
docker exec -it matrix-jitsi-prosody bashand then installcurland execute:Disabling Jitsi Authentication:
jitsi_enable_auth: false, Jitsi works without issues through both the native video button in Element and the Jitsi widget via Dimension.Keycloak Authentication:
Environment Information
References
The text was updated successfully, but these errors were encountered: