Hello,
We are trying to build on OpenVidu-3. The ReactJS app can connect to the LIVEKIT_URL when running from the local development server. However, it refuses to connect to the LIVEKIT_URL (wss://ourdomain.co) obtained from the OpenVidu Single Node Server.
Any insights on fixing this would be appreciated.
Thanks.
Hi,
Could you please explain how are you configured the tutorial for pointing to your single node deployment?
Hey,
Thanks for responding.
Here is what we did.
We followed the setup tutorial for the OpenVidu Single Node Installation (On-premises) as outlined in this link: OpenVidu Single Node Installation Tutorial.
sh <(curl -fsSL http://get.openvidu.io/community/singlenode/latest/install.sh )./opt/openvidu and started all services with the command: systemctl start openvidu.Can you let us know if we have missed any steps or did something wrong to disrupt the default settings that should work?
Could you please check if the enabled services, such as OpenVidu Call or OpenVidu Dashboard, are working properly?
If these service are working fine, the issue could be found on the application side. Maybe the configuration of the application-client or application server is wrong.
Do you have any error qhen trying to connect to the room?
How have you configured the React tutorial for working with your production deployment?
[quote="CSantosM, post:4, topic:5154”]
Could you please check if the enabled services, such as OpenVidu Call or OpenVidu Dashboard, are working properly?
[/quote]
It throws error while trying to use OpenVidu Call service. But it does connect to the dashboard.
Error logs:
1.Failed to load resource: the server responded with a status of 401 (Unauthorized)
2. [OpenViduService] ERROR: Error connecting to room: Error: could not establish pc connection
at main-LE5KMO62.js:49:15538
at I.<computed> (polyfills-6EAL64PA.js:1:21166)
at f.invokeTask (polyfills-6EAL64PA.js:1:7007)
at Object.onInvokeTask (main-LE5KMO62.js:7:59843)
at f.invokeTask (polyfills-6EAL64PA.js:1:6928)
at $.runTask (polyfills-6EAL64PA.js:1:2325)
at invokeTask (polyfills-6EAL64PA.js:1:8081)
at b.useG.invoke (polyfills-6EAL64PA.js:1:7981)
at E.T.args.<computed> (polyfills-6EAL64PA.js:1:20883)
3. SessionComponent] ERROR: There was an error connecting to the room: CONNECTION_ERROR Error connecting to the server at the following URL: wss://powerpodcast.co
It looks there is a problem with your deployment. Could you please send us the logs running the following command:
cd /opt/openvidu/
docker compose logs
*Be careful with the sensible information data
[quote="CSantosM, post:4, topic:5154”]
Here is our logs for
cd /opt/openvidu/
docker compose logs
minio
root@openvidu-single-node:/opt/openvidu# docker compose logs app minio
minio | 07:52:42.77 INFO ==>
minio | 07:52:42.77 INFO ==> Welcome to the Bitnami minio container
minio | 07:52:42.78 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers
minio | 07:52:42.78 INFO ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
minio | 07:52:42.78 INFO ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
minio | 07:52:42.78 INFO ==>
minio | 07:52:42.79 INFO ==> ** Starting MinIO setup **
minio | minio 07:52:42.98 INFO ==> Starting MinIO in background...
minio | minio 07:52:48.43 INFO ==> Adding local Minio host to 'mc' configuration...
minio | minio 07:52:48.77 INFO ==> Creating default buckets...
minio | Bucket created successfully `local/openvidu`.
minio | minio 07:52:49.03 INFO ==> Stopping MinIO...
minio |
minio | 07:52:49.13 INFO ==> ** MinIO setup finished! **
minio | minio 07:52:49.16 INFO ==> ** Starting MinIO **
minio | MinIO Object Storage Server
minio | Copyright: 2015-2024 MinIO, Inc.
minio | License: GNU AGPLv3 - https://www.gnu.org/licenses/agpl-3.0.html
minio | Version: DEVELOPMENT.2024-06-13T22-53-53Z (go1.21.11 linux/amd64)
minio |
minio | API: http://localhost:9100
minio | WebUI: https://powerpodcast.co/minio-console/
minio |
minio | Docs: https://min.io/docs/minio/linux/index.html
minio | Status: 1 Online, 0 Offline.
minio | STARTUP WARNINGS:
minio | - The standard parity is set to 0. This can lead to data loss.
minio |
minio | You are running an older version of MinIO released 1 month before the latest release
minio | Update: Run `mc admin update ALIAS`
minio |
minio |
dashboard
root@openvidu-single-node:/opt/openvidu# docker compose logs dashboard
dashboard | Pinging MongoDB...
dashboard | MongoDB is reachable
dashboard | OpenVidu Dashboard listening on port 5000
openvidu
app
redis
prometheus
[quote="CSantosM, post:4, topic:5154”]
egress
egress | + rm -rf '/home/egress/tmp/*'
egress | + rm -rf /var/run/pulse /var/lib/pulse /home/egress/.config/pulse /home/egress/.cache/xdgr/pulse
egress | + pulseaudio -D --verbose --exit-idle-time=-1 --disallow-exit
egress | I: [pulseaudio] main.c: Daemon startup successful.
egress | + exec egress
egress | 2024-08-05T07:52:44.156Z INFO egress redis/redis.go:142 connecting to redis {"nodeID": "NE_TckmYEUxTZFQ", "clusterID": "", "simple": true, "addr": "localhost:7000"}
egress | 2024-08-05T07:52:44.179Z INFO egress stats/monitor.go:169 cpu available: 4.000000 max cost: 0.010000 {"nodeID": "NE_TckmYEUxTZFQ", "clusterID": ""}
egress | 2024-08-05T07:52:44.181Z INFO egress service/service.go:143 service ready {"nodeID": "NE_TckmYEUxTZFQ", "clusterID": ""}
promtail
promtail | level=info ts=2024-08-05T07:52:44.232054868Z caller=promtail.go:133 msg="Reloading configuration file" md5sum=49509c33a83eeb6536b13cfa1df8f461
promtail | level=info ts=2024-08-05T07:52:44.236906664Z caller=server.go:334 http=[::]:9080 grpc=[::]:39157 msg="server listening on addresses"
promtail | level=info ts=2024-08-05T07:52:44.243384065Z caller=main.go:174 msg="Starting Promtail" version="(version=release-2.8.x-d198b22, branch=release-2.8.x, revision=d198b22)"
promtail | level=warn ts=2024-08-05T07:52:44.24373797Z caller=promtail.go:265 msg="enable watchConfig"
promtail | level=info ts=2024-08-05T07:52:49.235891151Z caller=target_group.go:128 msg="added Docker target" containerID=3ecc8e320efa8c2e368953813f5d3d582602d415186a3bdeb44b793b04408bc2
promtail | level=info ts=2024-08-05T07:52:49.235931745Z caller=target_group.go:128 msg="added Docker target" containerID=55aac9eaf6282d2890d154c3989937aea18d2c58d19f362e7fb82131750a2454
promtail | level=info ts=2024-08-05T07:52:49.235950367Z caller=target_group.go:128 msg="added Docker target" containerID=c0e4e0530def2867922e29ed1c190156c423cfd482404e69b199d0dc2c970fd0
promtail | level=info ts=2024-08-05T07:52:49.235965328Z caller=target_group.go:128 msg="added Docker target" containerID=56b86eaa3a8082e1bf0a8b1fe1af0500ebccf2f432eb60751c3606c18524ceda
promtail | level=info ts=2024-08-05T07:52:49.235985295Z caller=target_group.go:128 msg="added Docker target" containerID=34b9514a46cb5032e1920956ef9a1b01ac45f81590b2d266cf1e681bffae3bfe
promtail | level=info ts=2024-08-05T07:52:49.236013711Z caller=target_group.go:128 msg="added Docker target" containerID=cb47d76115f062dce98f792b94f4890d56fd623c1d96fb6b7f388d12c93dfc67
promtail | level=info ts=2024-08-05T07:52:49.236043506Z caller=target_group.go:128 msg="added Docker target" containerID=383fd5cb4285f962452b8caddecc9b139d690cb9d04fd4547bd48f6a23932289
promtail | level=info ts=2024-08-05T07:52:49.236097877Z caller=target_group.go:128 msg="added Docker target" containerID=8b00cec8006ea494cee63992e2e7cb5560d30d47aa1fd756063db77943de3bbb
promtail | level=info ts=2024-08-05T07:52:49.236127735Z caller=target_group.go:128 msg="added Docker target" containerID=92875820b2220a527c34893c5b6eb278e4fe642055cd65f944ecc9c6960088cd
ingress
ingress | 2024-08-05T07:52:42.327Z INFO ingress redis/redis.go:127 connecting to redis {"nodeID": "NE_MNnx3zYd2ctK", "simple": true, "addr": "localhost:7000"}
ingress | 2024-08-05T07:52:42.366Z INFO ingress whip/server.go:78 starting WHIP server {"nodeID": "NE_MNnx3zYd2ctK"}
ingress | 2024-08-05T07:52:43.398Z INFO ingress rtcconfig/webrtc_config.go:241 failed to get external ip {"nodeID": "NE_MNnx3zYd2ctK", "local": "172.17.0.1", "err": "could not validate external IP: 34.70.50.24"}
ingress | 2024-08-05T07:52:43.398Z INFO ingress rtcconfig/webrtc_config.go:241 failed to get external ip {"nodeID": "NE_MNnx3zYd2ctK", "local": "10.128.0.20", "err": "could not validate external IP: 34.70.50.24"}
ingress | 2024-08-05T07:52:47.370Z INFO ingress rtcconfig/webrtc_config.go:70 no external IPs found, using node IP for NAT1To1Ips {"nodeID": "NE_MNnx3zYd2ctK", "ip": "34.70.50.24"}
ingress | 2024-08-05T07:52:47.372Z WARN ingress stats/monitor.go:115 rtmp input requirement too low {"nodeID": "NE_MNnx3zYd2ctK", "config value": 0, "minimum value": 1, "recommended value": 2}
ingress | 2024-08-05T07:52:47.372Z WARN ingress stats/monitor.go:123 whip input requirement too low {"nodeID": "NE_MNnx3zYd2ctK", "config value": 0, "minimum value": 1, "recommended value": 2}
ingress | 2024-08-05T07:52:47.372Z WARN ingress stats/monitor.go:131 whip input with transcoding bypassed requirement too low {"nodeID": "NE_MNnx3zYd2ctK", "config value": 0, "minimum value": 0.05, "recommended value": 0.1}
ingress | 2024-08-05T07:52:47.372Z WARN ingress stats/monitor.go:139 url input requirement too low {"nodeID": "NE_MNnx3zYd2ctK", "config value": 0, "minimum value": 1, "recommended value": 2}
ingress | 2024-08-05T07:52:47.372Z INFO ingress stats/monitor.go:177 available CPU cores: 4.000000 max cost: 0.000000 {"nodeID": "NE_MNnx3zYd2ctK"}
If you need logs from Grafana, Caddy, Mongo, or Loki, please let us know, and we will provide them as separate text files
Hello @lily.menorah
Are you the same from this this issue?
Does your gcloud instance have a dedicated public IP
Can you screenshot your gcloud firewall/ports configuration?
It looks like the deployment is not able to receive candidates from your browser from a previous screenshot you’ve sent:
Please double check Ports Configuration
Send me a DM with your deployment credentials so we can test with our tutorials your deployment, just in case we can see any issue from there. You’re free to give us temporal SSH access if you want. If you can’t DM me, email me at carlos.ruiz@openvidu.io
Solved here:
