Hi team,
I am running openvidu in Linux, latest (3.1.0) docker version.
Deployment in compliance with the documentation.
I cannot reach the server, since it does not listen at IPv4 traffic.
This is what the logs say:
{“level”:“info”,“ts”:1742899326.4948359,“msg”:“using config from file”,“file”:“/config/caddy.yaml”}
{“level”:“info”,“ts”:1742899326.496607,“msg”:“adapted config to JSON”,“adapter”:“yaml”}
{“level”:“info”,“ts”:1742899326.497715,“msg”:“redirected default logger”,“from”:“stderr”,“to”:“stdout”}
{“level”:“warn”,“ts”:1742899326.4977381,“logger”:“admin”,“msg”:“admin endpoint disabled”}
{“level”:“warn”,“ts”:1742899326.498806,“logger”:“http.auto_https”,“msg”:“server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server”,“server_name”:“http_redirect”,“http_port”:80}
{“level”:“info”,“ts”:1742899326.4988337,“logger”:“http.auto_https”,“msg”:“skipping automatic certificate management because one or more matching certificates are already loaded”,“domain”:“openvidu.xy-space.de”,“server_name”:“minio”}
{“level”:“info”,“ts”:1742899326.4988472,“logger”:“http.auto_https”,“msg”:“enabling automatic HTTP->HTTPS redirects”,“server_name”:“minio”}
{“level”:“info”,“ts”:1742899326.5007923,“logger”:“http.log”,“msg”:“server running”,“name”:“http_redirect”,“protocols”:[“h1”,“h2”,“h3”]}
{“level”:“info”,“ts”:1742899326.500842,“logger”:“http”,“msg”:“enabling HTTP/3 listener”,“addr”:“:9000”}
{“level”:“info”,“ts”:1742899326.5010471,“logger”:“http.log”,“msg”:“server running”,“name”:“minio”,“protocols”:[“h1”,“h2”,“h3”]}
{“level”:“info”,“ts”:1742899326.5010722,“logger”:“http.log”,“msg”:“server running”,“name”:“public”,“protocols”:[“h1”,“h2”,“h3”]}
{“level”:“debug”,“ts”:1742899326.5010881,“logger”:“layer4”,“msg”:“listening”,“address”:“tcp/[::]:1935”}
{“level”:“debug”,“ts”:1742899326.5010972,“logger”:“layer4”,“msg”:“listening”,“address”:“tcp/[::]:443”}
{“level”:“info”,“ts”:1742899326.5012317,“msg”:“autosaved config (load with --resume flag)”,“file”:“/root/.config/caddy/autosave.json”}
{“level”:“info”,“ts”:1742899326.501236,“msg”:“serving initial configuration”}
{“level”:“debug”,“ts”:1742899382.4041414,“logger”:“layer4”,“msg”:“matching”,“remote”:“89.11.20.117:26174”,“error”:“consumed all prefetched bytes”,“matcher”:“layer4.matchers.tls”,“matched”:false}
{“level”:“debug”,“ts”:1742899382.4042,“logger”:“layer4”,“msg”:“prefetched”,“remote”:“89.11.20.117:26174”,“bytes”:517}
{“level”:“debug”,“ts”:1742899382.4042437,“logger”:“layer4”,“msg”:“matching”,“remote”:“89.11.20.117:26174”,“matcher”:“layer4.matchers.tls”,“matched”:true}
netstat -tulpn gives me:
tcp6 0 0 :::443 :::* LISTEN 141102/caddy
udp 0 0 0.0.0.0:443 0.0.0.0:* 141347/livekit-server
I want caddy to listen for IPv4 requests as well, how to manage that???
Interestingly, livekit-server listens for IPv4 connections.
I defined the server name with intitial configuration, no IP address. Maybe I should define the IP instead?
Martin.