timeout lookup user info should retry

[escix]

Sometimes the userinfo url timeout to get the user info during element-call.

Then the call just hangs without any progress.

if the lk-jwt-service get a timeout then the service should retry to get the userinfo.

[BillCarsonFr]

Hello escix,

Can you give more details on what happens currently if there is a timeout? What is the experience on your side? Is there an error that is handled (or not) by the client?

[escix]

@BillCarsonFr I noticed that accidentally due to a misconfiguration in the DNS server (unbound).

When I make a call the lk-JWT-service will get the token from homeserver, however in some cases it just timeout (as it is unable to go through other processes due to domains not resolving.).

In this case the client just waiting for lk-JWT-service to connect to livekit which never happens. The lk-JWT-service log just spits out error saying it is timeout on getting user info from synapse.

In my case (due to DNS resolution error) some of the calls connected then also waited forever to connect to turnserver with the Waiting for Media info on the client.

[Beleggrodion]

I had a similar issue on my test system because all docker images are on the same server and the server (because is behind a firewall) cannot call the public ip directly. I added the domain, which is local, as extra hosts in my docker compose file for the specific domain:

    extra_hosts:
      - "matrix.demo.domain.com:192.168.x.x"