https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# helpdesk
s
This message was deleted.
c
Check the config file. Looks like you have issues with YAML 🙂
f
Which YAML file i have to check ?
c
The Caddy one? as log message is generated by Caddy?
f
I am not able to see file /etc/caddy.yaml at given path .
c
it’s not on /etc/caddy.yaml
it was generated by config generator most probably:
Copy code
docker run --rm -it -v$PWD:/output livekit/generate
f
ok
c
right? In that directory, you have caddy.yaml
and it’s being mounted for caddy in docker-compose.
isn’t it?
depending on options, you probably also got init-script. Which put all stuff under /opt/livekit
Also, if you picked to use redis, you might need to add redis IP
f
Yes i did that step or getting successfully log ,But also getting this error also .
d
That's not an error..
f
@dry-elephant-14928 I am not able to connect .
livekit-caddy-1 | {"level":"info","ts":1642786068.3883107,"logger":"tls.obtain","msg":"certificate obtained successfully","identifier":"<yourhost>"} Not getting this logs
c
is livekit.creole.tech resolving to that IP? Also for turn?
f
Got caddy server below error . livekit-caddy-1 | run: adapting config using yaml: error converting YAML to JSON: yaml: line 15: did not find expected key
@cuddly-alarm-64312 i don't get your point .
c
I mean, do domains configured has proper DNS records pointing to correct IP. Caddy is trying to get cert, and it needs that LetsEncrypt can reach it 🙂
can you share caddy.yaml?
f
Copy code
logging:
  logs:
    default:
      level: INFO
storage:
  "module": "file_system"
  "root": "/data"
apps:
  tls:
    certificates:
      automate:
         - livekit.creole.tech
        - livekit-turn.creole.tech
  layer4:
    servers:
      main:
        listen: [":443"]
        routes:
          - match:
            - tls:
                sni:
                  - livekit-turn.creole.tech
            handle:
              - handler: tls
              - handler: proxy
                upstreams:
                  - dial: ["172.31.33.84:5349"]
          - match:
              - tls:
                  sni:
                    - livekit.creole.tech
            handle:
              - handler: tls
                connection_policies:
                  - alpn: ["http/1.1"]
              - handler: proxy
                upstreams:
                  - dial: ["localhost:7880"]
c
identation error:
Copy code
automate:
         - livekit.creole.tech
        - livekit-turn.creole.tech
these lines
f
What i have to do ?
c
-
should be at same place
f
ok
c
Copy code
apps:
  tls:
    certificates:
      automate:
        - livekit.creole.tech
        - livekit-turn.creole.tech
here 😄
single extra space is destroying a lot 🙂
@few-flag-99144 have it helped?
f
Yes @cuddly-alarm-64312 Caddy image service working but not got the this log livekit-caddy-1 | run: adapting config using yaml: error converting YAML to JSON: yaml: line 15: did not find expected key
c
do docker-compose down / up. as i think it havent reread file.
✅ 1
it’s still same error.
and same line.
also, depending if you used script, or so, maybe you modify wrong file. might be another one in 
/opt/livekit/
🙂
f
Copy code
livekit-caddy-1    | {"level":"info","ts":1667981683.5289445,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/data"}
livekit-caddy-1    | {"level":"info","ts":1667981683.5295355,"logger":"tls","msg":"finished cleaning storage units"}
livekit-caddy-1    | {"level":"info","ts":1667981683.5306995,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc00018a930"}
livekit-caddy-1    | {"level":"info","ts":1667981683.5312235,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc00018a930"}
livekit-caddy-1    | {"level":"info","ts":1667981683.532474,"logger":"tls.obtain","msg":"acquiring lock","identifier":"livekit.creole.tech"}
livekit-caddy-1    | {"level":"info","ts":1667981683.5355885,"logger":"tls.obtain","msg":"lock acquired","identifier":"livekit.creole.tech"}
livekit-caddy-1    | {"level":"info","ts":1667981683.5361135,"logger":"tls.obtain","msg":"releasing lock","identifier":"livekit.creole.tech"}
livekit-caddy-1    | {"level":"error","ts":1667981683.5366874,"logger":"tls","msg":"job failed","error":"livekit.creole.tech: obtaining certificate: context canceled"}
livekit-caddy-1    | {"level":"info","ts":1667981683.5374055,"logger":"tls.obtain","msg":"acquiring lock","identifier":"livekit-turn.creole.tech"}
livekit-caddy-1    | {"level":"info","ts":1667981683.5407,"logger":"tls.obtain","msg":"lock acquired","identifier":"livekit-turn.creole.tech"}
livekit-caddy-1    | {"level":"info","ts":1667981683.5411952,"logger":"tls.obtain","msg":"releasing lock","identifier":"livekit-turn.creole.tech"}
livekit-caddy-1    | {"level":"error","ts":1667981683.5416818,"logger":"tls","msg":"job failed","error":"livekit-turn.creole.tech: obtaining certificate: context canceled"}
livekit-caddy-1    | run: loading initial config: loading new config: layer4 app module: start: listen tcp :443: bind: address already in use
livekit-caddy-1 exited with code 1
livekit-caddy-1    | {"level":"info","ts":1667981709.3390126,"msg":"using provided configuration","config_file":"/etc/caddy.yaml","config_adapter":"yaml"}
livekit-caddy-1    | {"level":"info","ts":1667981709.3407838,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
livekit-caddy-1    | {"level":"info","ts":1667981709.347927,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc000386700"}
livekit-caddy-1    | {"level":"info","ts":1667981709.3486738,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc000386700"}
livekit-caddy-1    | run: loading initial config: loading new config: layer4 app module: start: listen tcp :443: bind: address already in use
livekit-caddy-1 exited with code 1
livekit-caddy-1    | {"level":"info","ts":1667981760.7308571,"msg":"using provided configuration","config_file":"/etc/caddy.yaml","config_adapter":"yaml"}
livekit-caddy-1    | {"level":"info","ts":1667981760.7336779,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
livekit-caddy-1    | {"level":"info","ts":1667981760.7361634,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc000224690"}
livekit-caddy-1    | {"level":"info","ts":1667981760.7367096,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc000224690"}
livekit-caddy-1    | run: loading initial config: loading new config: layer4 app module: start: listen tcp :443: bind: address already in use
c
From which directory you run it?
the generator generates a few files, including docker-compose and install_script. Install script -> install it to /opt/livekit, and creates systemd unit.
f
opt/livekit
c
might me you have multiple caddy’s?
a simple docker ps might help
f
ok , i will check .
c
or go to /opt/livekit, do docker-compose down, and then:
Copy code
systemctl stop livekit-docker

systemctl start livekit-docker
f
ok @cuddly-alarm-64312 🙂
Hi @cuddly-alarm-64312 Its working fine i did the caddy.yml file formatting and kill the process of port 446. But i have a one issue , once two user call is on and some other users connect so existing users call refresh and reconnect , Why its happed ?
c
Are you sure u are using unique usernames? Like, if you connect user A, user B, user A, first session of user A gets kicked 🙂
f
Not kicked but reconnect , some time got live kit connection error.
consistency is disturbed.
c
I won’t be able to answer this 😄 I’m also a livekit user, not a dev 😄
f
Is memory issue or any thing else ?
ok @cuddly-alarm-64312 Thanks man for kind help 🙂
@dry-elephant-14928 Do you have a idea ?
4 Views
Open in Slack
PreviousNext
Powered by