Openvidu-server:3.0.0-beta2 is throwing 502

Issues with deployments
1

Hi Team,

I have installed openvidu-server:3.0.0-beta2 on Amazon Linux 2023 recently. However, when accessing DOMAIN_OR_PUBLIC_IP provided during deployment, we endup getting 502 Bad Gateway.

 docker ps
CONTAINER ID   IMAGE                                     COMMAND                  CREATED         STATUS          PORTS     NAMES
0ea3c2b3ce09   mongo:7.0.11                              "docker-entrypoint.s…"   9 minutes ago   Up 9 minutes              mongo
b7e7df25b198   bitnami/minio:2024.6.13                   "/opt/bitnami/script…"   9 minutes ago   Up 47 seconds             minio
687da205fe09   livekit/egress:v1.8.2                     "/entrypoint.sh"         9 minutes ago   Up 9 minutes              egress
f0df3995a68d   redis:7.2.5-alpine                        "docker-entrypoint.s…"   9 minutes ago   Up 9 minutes              redis
548defcc27b7   openvidu/openvidu-caddy:3.0.0-beta2       "/bin/caddy run --co…"   9 minutes ago   Up 9 minutes              caddy
df0c278f31b4   openvidu/openvidu-call:3.0.0-beta2        "docker-entrypoint.s…"   9 minutes ago   Up 9 minutes              app
f11194bf6eff   livekit/ingress:v1.2.0                    "ingress"                9 minutes ago   Up 9 minutes              ingress
80e906dd3cdc   openvidu/openvidu-server:3.0.0-beta2      "/livekit-server --c…"   9 minutes ago   Up 9 minutes              openvidu
3874a7351dda   openvidu/openvidu-dashboard:3.0.0-beta2   "./openvidu-dashboard"   9 minutes ago   Up 9 minutes              dashboard

I tried checking caddy container logs, ingress logs however there is nothing helpful. Please can you let me know how to figureout the reason for 502 in latest deployment.

 curl http://localhost:6080 -I
HTTP/1.1 200 OK
X-Powered-By: Express
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Last-Modified: Tue, 16 Jul 2024 15:46:27 GMT
ETag: W/"cbcd-190bc394038"
Content-Type: text/html; charset=UTF-8
Content-Length: 52173
Date: Fri, 13 Sep 2024 06:56:53 GMT
Connection: keep-alive
Keep-Alive: timeout=5

curl http://localhost:7880/ -I
HTTP/1.1 200 OK
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Content-Length: 52173
Content-Type: text/html; charset=UTF-8
Date: Fri, 13 Sep 2024 06:56:55 GMT
Etag: W/"cbcd-190bc394038"
Last-Modified: Tue, 16 Jul 2024 15:46:27 GMT
Server: Caddy
X-Powered-By: Express
2

Which URL is giving you a 502?

Did you modified something of the configuration? What parameters did you used?

3

Hi @cruizba Thanks for response. I am hitting domain URL with https:// and its thrown 502, I have disabled monitoring stack and no other changes are made to configs.

4
  • What are the logs of:
docker logs app
  • Can you reach these URLs?:
https://<your_domain>/twirp/health
https://<your_domain>/minio-console/
https://<your_domain>/dashboard/
  • Do you have another proxy in front of caddy?