MiroTalk Update regularly fails after update

[avatar1024]

I have had that happened with Mirotalk too,. Sometimes update get stuck. Happens less often these days but still sometimes. I either have to restart the app or remove and reinstall.

[MiroTalk]

Port allocation behavior

By default, when SFU_SERVER is set to false, the application uses a range of 100 ports.

when SFU_SERVER=true it allocate ports starting from 40000 default + CPU core eg if your server has 4CPU so become 40000 - 40003 (only 3 ports needed)

More about: https://mediasoup.discourse.group/t/mediasoups-webrtcserver-concerning-firewall-settings-and-port-binding/5965/5

---

Cloudron integration

To support this behavior on Cloudron, SFU_SERVER should be exposed as a toggle (switch button) in the MiroTalk SFU app settings (Location).
When the switch is enabled, the port allocation logic in start.sh can be updated something as follows:

# Enable / disable SFU server (default: false)
readonly SFU_SERVER="${SFU_SERVER:-false}"

# Number of CPU cores (used only when SFU is enabled)
readonly CPU_CORES="$(nproc)"

# Base TCP port (default: 25000)
readonly SFU_TCP_BASE="${SFU_TCP:-25000}"

if [[ "$SFU_SERVER" == "true" ]]; then
    # SFU enabled:
    # allocate one port per CPU core
    readonly SFU_MAX_PORT=$(( SFU_TCP_BASE + CPU_CORES - 1 ))
else
    # Default behavior:
    # allocate 100 ports starting from the base port
    readonly SFU_MAX_PORT=$(( SFU_TCP_BASE + 100 ))
fi

---

Benefits of this approach

• Fewer ports allocated
  Only the ports that are actually needed are opened, especially in SFU mode.

• Reduced port conflicts
  Smaller port ranges significantly lower the chance of clashes with other services on the same host.

• Better Cloudron compatibility
  Minimal port exposure aligns well with Cloudron’s strict networking and security model.

• Scales with hardware
  Port allocation automatically adapts to the number of CPU cores available.

• User control
  Exposing SFU_SERVER as a switch allows users to explicitly choose whether to run in SFU mode or keep the default behavior.

[james]

Hello @mirotalk
Does this have any other effects?

[MiroTalk]

@james said in MiroTalk Update regularly fails after update:

Does this have any other effects?

In theory, it shouldn’t have any other effects, as long as the user can switch between these two modes. I’m not entirely sure why Mediasoup doesn’t use a server SFU by default, but you could ask the Mediasoup support forum for clarification.

[djxx]

Is there any update on this? I can't rely on this app for meeting links because about 75% of the time it's not running properly due to startup failure.

[nebulon]

So this always happens when the app gets updated?

[djxx]

@nebulon It also happens after system updates or restarts. It seems it's a roll of the dice if the ports aren't already taken. Restarting the app doesn't fix it anymore, so now when it crashes I change the SFU TCP/UDP port range to something else and it works when the app restarts.

[robi]

Sounds like a firewall cleanup issue or maybe something in between

[nebulon]

When this happens, can you check which container is occupying those ports?

You can run

docker ps --format "table {{.ID}}\t{{.Names}}\t{{.Ports}}" | grep <portnumber>

which should reveal the container holding on to it.

[MiroTalk]

@djxx said:

Restarting the app doesn't fix it anymore, so now when it crashes I change the SFU TCP/UDP port range to something else and it works when the app restarts.

This issue can occur if another application is already using ports within the 40000–40100 range. To resolve it, you can either change the port range (for example, starting from 25000)

or enable WebRTC server mode in the env (edit it via Cloudron file manager), which requires fewer ports, as described above.

SFU_SERVER=true

Then restart the instance.