MiroTalk Update regularly fails after update
-
Description
MiroTalk SFU regularly gets stuck during the automatic update process:
Docker Error: (HTTP code 500) server error - failed to set up container networking: driver failed programming external connectivity on endpoint a877975d-38be-4088-bc92-e0d7a486a818 (2e5adaa635a95bd65ca0f290712065d444528e3420c49f2f88323b40c62caaa5): failed to bind host port for 0.0.0.0:40014:172.18.16.130:40014/tcp: address already in use
Steps to reproduce
Not sure. It happens during updates though.
Troubleshooting Already Performed
I've stopped the app, tried to retry the upgrade, retry the configure task. Sometimes it works after a few tries, other times I have to restart the server first.
System Details
Hetzner
vServer
4 Core "AMD EPYC-Milan Processor"
16.37 GB RAM & 4.29 GB SwapCloudron Version
9.0.15
Ubuntu Version
24.04
Output of
cloudron-support --troubleshootLinux: 6.8.0-88-generic Ubuntu: noble 24.04 Execution environment: kvm Processor: AMD EPYC-Milan Processor BIOS NotSpecified CPU @ 2.0GHz x 4 RAM: 15989992KB Disk: /dev/sda1 44G [OK] node version is correct [OK] IPv6 is enabled in kernel. No public IPv6 address [OK] docker is running [OK] docker version is correct [OK] MySQL is running [OK] nginx is running [OK] dashboard cert is valid [OK] dashboard is reachable via loopback [OK] No pending database migrations [OK] Service 'mysql' is running and healthy [OK] Service 'postgresql' is running and healthy [OK] Service 'mongodb' is running and healthy [OK] Service 'mail' is running and healthy [OK] Service 'graphite' is running and healthy [OK] Service 'sftp' is running and healthy [OK] box v9.0.15 is running [OK] netplan is good [OK] DNS is resolving via systemd-resolved [OK] Dashboard is reachable via domain name [WARN] Domain domain.com expiry check skipped because whois does not have this information [OK] unbound is running -
Hello @djxx
This is a common issue and has been reported multiple times.
Please try to stop the app, wait a minute and then attempt the update process again.
If this still fails, please stop the app again.
Then connect with ssh to your server.Since your error is the following:
Docker Error: (HTTP code 500) server error - failed to set up container networking: driver failed programming external connectivity on endpoint a877975d-38be-4088-bc92-e0d7a486a818 (2e5adaa635a95bd65ca0f290712065d444528e3420c49f2f88323b40c62caaa5): failed to bind host port for 0.0.0.0:40014:172.18.16.130:40014/tcp: address already in useit reveals you have changed the ports to 40000 'ish.
Could you please confirm what port you have chosen?
From the ports you have chosen you can run the following command in ssh to see if any other application is already using the the ports:
If you have chosen40000then the Mirotalk app uses 100 ports of so40000to40100.lsof -i :40000-40100 -
Hello @djxx
This is a common issue and has been reported multiple times.
Please try to stop the app, wait a minute and then attempt the update process again.
If this still fails, please stop the app again.
Then connect with ssh to your server.Since your error is the following:
Docker Error: (HTTP code 500) server error - failed to set up container networking: driver failed programming external connectivity on endpoint a877975d-38be-4088-bc92-e0d7a486a818 (2e5adaa635a95bd65ca0f290712065d444528e3420c49f2f88323b40c62caaa5): failed to bind host port for 0.0.0.0:40014:172.18.16.130:40014/tcp: address already in useit reveals you have changed the ports to 40000 'ish.
Could you please confirm what port you have chosen?
From the ports you have chosen you can run the following command in ssh to see if any other application is already using the the ports:
If you have chosen40000then the Mirotalk app uses 100 ports of so40000to40100.lsof -i :40000-40100
