Mirotalk - Participants can't see each other 2

[ekevu123]

Thank you for explaining! If it happens next time again, I will look through port usage on the server.

[james]

Hello @ekevu123 and @mirotalk-57bab571
I have figured out what the issue is with changing ports.
An app update will be available soon that fixes this issue.

[MiroTalk]

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

I have figured out what the issue is with changing ports.
An app update will be available soon that fixes this issue.

Good!

[ekevu123]

@james This issue is back

[james]

Hello @avatar1024
I was unable to reproduce this issue.
Changed the ports from 25000 to 30000 and tested with my desktop and mobile phone with no issues.

[ekevu123]

It has worked again now after changing the port and restarting the app. Does it need to be any port between 25000 and 30000?

[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.