Sebastian Denz

Problem still exists... It doesnt matter if i use the loki-local-config.yaml from the repo or the one from above..

I did: * docker-compose down * mv loki/loki-local-config.yaml /tmp/ * docker-compose up But nothing changed...

I know.. but to me there is very little information in the logs... ``` [0][root@siptrace:~]# docker logs loki failed parsing config: /etc/loki/local-config.yaml: not a valid duration string: "0" failed parsing...

> You can set enable_domain_verification = false and it will work. > > This is duplicate of #11999 I will try to look at it next week. > > The...

It is TURN_CREDENTIALS instead of TURN_CREDENTIAL - see https://github.com/jitsi/docker-jitsi-meet/blob/master/prosody/rootfs/defaults/conf.d/jitsi-meet.cfg.lua#L85

I just realized that i forgot to mention.. in addition to the logged error message our clients start to get connection issues as well, so we have to restart Kamailio...

@sergey-safarov yes we do :)  @miconda at the moment we do the tls.reload unconditionally and quite 'high frequently' to ensure the CRLs are up to date.. of course we...

 This Screenshot is from our dev environment (with no tls-clients connected) running: ``` while true ; do /usr/sbin/kamcmd tls.reload ; /usr/sbin/kamcmd tls.reload ; sleep 0.5 ; done ``` Parallel...

The problem actually occured after we added the CRL some weeks ago.. without CRL there was no such behaviour. And of course there are a lot options to mitigate the...

Although it is quite easy to monitor and workaround this issue - i still think it is a valid bug :)