Mirotalk - Participants can't see each other 2

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

[ekevu123]

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

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

Netcup, root server
Don't forget, though, that the issue isn't permanent.

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

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

Thank you! I only let Cloudron handle this.

[james]

Hello @ekevu123
Next time the issue occurs please save the following logs

• The MiroTalk SFU app log
• the browser console log and network inspection log
• /home/yellowtent/platformdata/logs/box.log
• While this issue is occouring in the browser do:
  • Chrome based browsers go to brave://webrtc-internals/ and press Download the "webrtc-internals dump
  • FireFox based browsers go to about:webrtc and press Save Page

This will help us to further narrow down the cause.

[ekevu123]

It has happened again and I was able to catch a few issues that might be related:

1. WebRTC: ICE failed, add a STUN server and see about:webrtc for more details
2. Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://translate.googleapis.com/element/log?format=json&hasfast=true&authuser=0. (Reason: CORS request did not succeed). Status code: (null).
3. Consumer Transport failed
   Object { id: "9d932828-8aba-4b93-af58-235cb3a06c1b" }

/home/yellowtent/platformdata/logs/box.log - doesn't contain anything related to mirotalk

Network logs: lists that umami is failing (probably blocked by plugin) and googletranslate (see above)

I am sending about:webrtc via e-mail, because it is a huge fail and contains personal information.

[ekevu123]

I just wanted to see if anyone has an idea regarding this?

[james]

Hello @ekevu123
Could it be that you are behind a NAT?

[ekevu123]

Not knowingly!

Did you check the data I sent via email?

[james]

Hello @ekevu123
Yes, I got the mail and reviewed the WebRTC log.
But could not pinpoint the issue from it.

I would like you to run a test.
If it fails once again on your desktop client. Please try to connect to the meeting with two clients that are connected with Mobile data (LTE/5G), so outside your network.
With that, I want to make sure that the issue is not related to your local network.
If the two external clients can connect and use @mirotalk-57bab571 without any issue, we know where to look next.

Also, did you set SFU_SERVER=true in your /app/data/env file as suggested by @mirotalk?

[ekevu123]

You might be on to something here. When I tried to set up a call with myself just now, the issue occurred, but when I switched to mobile hotspot, I could connect. It could be that the co-working I am usually in blocks this, and I didn't realise this pattern, so I assumed this was an irregular failure.
I'll test this again later, just to be sure, but you might have solved the mystery, thanks a bunch!

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

Also, did you set SFU_SERVER=true in your /app/data/env file as suggested by @mirotalk?

Yes!