Mirotalk - Participants can't see each other 2

[james]

Hello @ekevu123
No. I've also just tested with port 5000.
But the ports need to be free since 100 ports will be used.
So if you set the port to 5000, from port 5000 to port 5100 will be used.
If a port in that range is used by another application, the mirotalk application will have issues.

[MiroTalk]

@james said in Mirotalk - Participants can't see each other 2:

If a port in that range is used by another application, the mirotalk application will have issues.

You can try to enable the WebRtcServer feature by adding the following to your env file:

SFU_SERVER=true

Then, RESTART your instance.

How it works:

• MiroTalk spawns one Worker per CPU core by default.
• Each Worker runs its own WebRtcServer on a dedicated port.
• Ports are assigned sequentially starting from a base port (eg: 25000).
• This approach keeps port management simple: you only need to open as many ports as you have Workers.

Optional: You can manually set the number of Workers using:

SFU_NUM_WORKERS=4

Example:
A server with 4 CPU cores (or 4 Workers) and a base port of 25000 will use the following ports:

25000, 25001, 25002, 25003

You only need to open these 4 ports on your firewall.

More about here

[ekevu123]

Thank you, I will try that!

Since I faced the issue temporarily yesterday, but didn't when I tried to reproduce it with my phone, is the explanation that the port I was trying to use for the conversation was temporarily blocked, and restarting the app later re-assigned the port, so it worked again when starting a new conversation?

[MiroTalk]

You're welcome.
It could also be that another app was using a port within the specified range, maybe not constantly, but whenever it needed it, causing a temporary conflict.

[ekevu123]

That would indeed explain it, but - and that is probably a question to the Cloudron team - shouldn't Cloudron prevent exactly that?

[ekevu123]

I keep having the issue sporadically, which makes it hard to use Mirotalk as a constant video provider without testing the connection before every meeting.

[james]

Hello @ekevu123
Thanks for reporting.

I would rule out the networking issue with the ports since Cloudron does bind these ports on app startup.
Thus, the ports could only interfere on app startup, failing to start the app and not at runtime.
You can check this with:

lsof -i :25000-25100

So there must be something else going on for you.
Is there any pattern to this sporadically appearing issue?

[ekevu123]

No, I can't find any pattern, but I have just tested again after a server restart, and the issue persists

[james]

Hello @ekevu123
Can you share where you are hosting your Cloudron?

[MiroTalk]

Also make sure that the firewall on your VPS/VDS is not enabled or blocking the required ports. For example, on Amazon EC2, if the inbound security group rules for the necessary RTC ports are not configured, the service will not work...