search

jitsi / jitsi-meet-sdk-samples

Jitsi Meet mobile SDK examples (Android, iOS and React Native)
Apache License 2.0
270 stars 235 forks source link

Not working with URL IP address #148

Closed Rainbow87 closed 2 years ago

Rainbow87 commented 2 years ago

I setup local server using ip address. I install Jitsi Meet app from Play Store, enter URL is 192.168.x.x and can join meeting room OK But with app build from jitsi-meet-sdk-samples, cannot join the room, it's shows error message "You have been disconnected. You may want to check your network connection. Reconnecting in 25 sec..."

How can i fix this problem?

1433498251 commented 1 year ago

Could you tell me how to solve it

saghul commented 1 year ago

It's not possible, you need a valid TLS certificate.

1433498251 commented 1 year ago

It's not possible, you need a valid TLS certificate.

A valid TLS certificate has been configured, but the same problem still exists. What else should I pay attention to

saghul commented 1 year ago

Make sure the full cert chain is offered by your web server.

Do you get any warnings in safari?

1433498251 commented 1 year ago

Make sure the full cert chain is offered by your web server.

Do you get any warnings in safari?

Safari has no warnings. My environment is Android. I have tried SDK 7.0.0 and 5.1.0. The server version is 7577. All have this problem. Can you tell me whether this problem is related to the version? Or what other precautions, debugging methods. Thank you very much

saghul commented 1 year ago

If you test your server here: https://whatsmychaincert.com/ does it say it's ok?

I have tried SDK 7.0.0 and 5.1.0. The server version is 7577. All have this problem.

Using an IP address has never worked, it's not an SDK / server limitation, but an iOS / Google one.

1433498251 commented 1 year ago

If you test your server here: https://whatsmychaincert.com/ does it say it's ok?

I have tried SDK 7.0.0 and 5.1.0. The server version is 7577. All have this problem.

Using an IP address has never worked, it's not an SDK / server limitation, but an iOS / Google one. This problem was solved because the certificate was used incorrectly. Excuse me, stable/jitsi meet_7577 Which version of the mobile SDK correspond to