mynaparrot / plugNmeet-server

WebRTC based Scalable, High Performance, Open source web conferencing system using Livekit.
https://www.plugnmeet.org
MIT License
305 stars 75 forks source link

install script is not working #579

Closed jhjacobs81 closed 2 weeks ago

jhjacobs81 commented 2 weeks ago

So following this page: https://www.plugnmeet.org/docs/installation i created an Ubuntu 22.04 LTS VPS with nothing on it. i then execute: sudo su -c "bash <(wget -qO- https://raw.githubusercontent.com/mynaparrot/plugNmeet-install/main/install.sh)" root Which installs a bunch of software, add docker containers etc. it runs all the way up untill these error messages:


haproxy[5744]: backend bk_plugnmeet_server has no server available!

Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:17 UTC):

haproxy[5744]: backend bk_plugnmeet_server has no server available!

Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:18 UTC):

haproxy[5744]: backend bk_etherpad has no server available!

Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:18 UTC):

haproxy[5744]: backend bk_etherpad has no server available!

Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:18 UTC):

haproxy[5744]: backend bk_etherpad has no server available!

Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:18 UTC):

haproxy[5744]: backend bk_etherpad has no server available!

.
Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:18 UTC):

haproxy[5744]: backend bk_ingress has no server available!

Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:18 UTC):

haproxy[5744]: backend bk_ingress has no server available!

Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:18 UTC):

haproxy[5744]: backend bk_ingress has no server available!

Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:18 UTC):

haproxy[5744]: backend bk_ingress has no server available!

Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:19 UTC):

haproxy[5744]: proxy rtmp has no server available!

Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:19 UTC):

haproxy[5744]: proxy rtmp has no server available!

Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:19 UTC):

haproxy[5744]: proxy rtmp has no server available!

Broadcast message from systemd-journald@domain.tld (Tue 2024-10-29 15:50:19 UTC):

haproxy[5744]: proxy rtmp has no server available!

After which follows an endless stream of '............' and the server shows only: 503 Service Unavailable No server is available to handle this request.

in the browser.

jhjacobs81 commented 2 weeks ago

trying it on Debian 12 isnt working either :(

image

jhjacobs81 commented 2 weeks ago

For future reference: this was due to 3 CPU's instead of the minimal 4. idealy, the script would report this at the start and not continue at all, but alas!