-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error 1020 when connection BBB via iOS #10746
Comments
Can you check if your STUN/TURN configurations were overwritten in bbb-web? |
I have the same problem, probably after an upgrade on last weekend. My server is not behind a NAT firewall, so I never changed anything in the STUN/TURN configuration. |
I am with the same problem. I have Stun configured. Was working perfect before the iOS upgrade. I checked with many devices, but all of them was with version 13.7... |
I have the same problem. It worked Monday October 26 on several iPads. It is since Wednesday October 28 that the activation of the camera systematically fails on Safari. I tested this on Safari 14.0 (15610.1.28.1.9, 15610) on MacOS 10.15.7 and iPadOS 14.1. On MacOS, no problem with Firefox and Chrome. Does Apple silently update Safari? |
The problem is, if you try to use the Chrome on Iphone, it doesn´t allow. Appears a message saying that is recommended using the Safari for better performance... I don´t know in english what is the message, but it´s something like these. |
We have the same issue. Opened it up here #10747 I think the entire Safari Compatibility broke. The issue is on Bountysource as well. |
Please do not mix 2.2 and 2.3 issues, if possible. 2.3 users, issue 10747. For the "me too" folks: please try test.bigbluebutton.org (2.2), and see if it works. It's the minimum you can do to make things easier for us to see if this is a real issue or a configuration issue.
Your server not being on NAT isn't the point. I was talking about the bbb-web STUN configuration, which is for the end users. A reliable a STUN server and preferably a TURN server as well must be configured if you want to expect it to always work. Can you confirm which STUN server are you using in bbb-web? Docs here: https://docs.bigbluebutton.org/2.2/setup-turn-server.html#configure-bigbluebutton-to-use-the-coturn-server. |
@prlanzarin Indeed, it works on test.bigbluebutton.org. It seems to be a configuration issue. |
For those that upgraded to 2.2.28, can you try specifying the following values for
Restart BigBlueButton and then try joining a session with iOS and share a webcam. Let us know if that works. |
Nope this did not work for me. Here are the things I have tried so far
the issue started appearing on safari browsers all of a sudden without any config change on our servers (running on AWS c5.xlarge instance) |
I solved error 1020 for some MacOS users by adding port information to Second problem was STUN/TURN server wasn't able to accept IPv6. So I've configured IPv6 (address, firewall) and error 1020 was solved for more MacOS users. Also consider https://docs.bigbluebutton.org/2.2/troubleshooting#configure-bigbluebuttonfreeswitch-to-support-ipv6 if your BBB is available via IPv6. I'm not sure this case is correct: Kind regards |
Well, if I understand correctly, the STUN server is configured in /usr/share/bbb-web/WEB-INF/classes/spring/turn-stun-servers.xml as stun.freeswitch.org, I never changed that file, it is the original file from package bbb-web. |
We upgraded from 2.2.26 to 2.2.28 |
So the port number for If you use still use Hint: Please use copy and paste. There is a lower case L and not a number 1 :-) |
@timm2k |
sorry ;-) |
as @ffdixon suggested |
Just tried that. It's working in a dev server I set up and working in test.bigbluebutton.org. So it's probably a configuration issue. You're on AWS. AWS EC2 instances are usually behind NAT. Did you set up a STUN in Kurento? If so, are you sure it's still working? https://docs.bigbluebutton.org/2.2/configure-firewall#extra-steps-when-server-is-behind-nat Steps here to check that. |
Setting the stun server to stun.1.google.com:19302 solved the problem for me. |
Changing the stun server settings works for us as well |
just wanted to add: still using 2.2.23 and suddenly the same experience, using Safari on iPadOS 14 Webcams stopped working, throwing error 1020, but also Safari using MacOS Catalina 10.15.7. Alternatively using Firefox on the same devices - mobile and MacOS - worked flawless. Following advise above changing the stun server entry from freeswitch to google server resolved the issue and now Safari on either MacOS and iOS devices is working again. Seems to be Safari related issue. |
Hi dear @ffdixon I even try test.bigbluebutton.org and it doesn't work too. (shows error 1020) Please help me to solve this problem. I explain completely in this topic |
Regarding that some people have success with test.bigbluebutton.org and some don't - we managed to reproduce that bit at least (though not 100% sure what to make from it). From Home-WiFi with "real" IPv4-Adress and "fake" IPv6 via 6to4 tunnel from the Fritzbox, test.bigbluebutton.org does NOT work. So what remains is: Sorry, I was hoping for more :( Edit: all testet with iOS 14.0 from an iPhone and iPadOS 14.1 from an iPad... |
Changing to stun.l.google.com:19302 fixed several issues for me, including the echo test taking very long to load (about 30 seconds) and sometimes not working, and also fixed the webcam on macOS / Safari 14. |
Same here on our own servers - couldn't try it yesterday because the servers were actively used, but now with the Google-STUN-server, all works. For whichever reason, test.bigbluebutton.org ALSO works now from whichever internet-connection. |
For me too. |
Hi there,
` is there anything wrong with this? i also get the 1020 on ios The turn server is working just ios is acting up |
@DDQW have you at least tested it on test.bigbluebutton.org? |
Hello, I checked that I have no AAAA-record set. `
` |
My config currently looks the same. |
I have also updated the Turn-Servers with:
Now it seems to work for the version 2.2.36. |
I'm going crazy, I have fixed this issue a couple days ago on my servers and it is back not working on the macOS and iOS devices... |
@coderDem in case you have a macOS device for testing, install
What is your output? |
Hello, my output is:
It is weird after I made the same:
The sharing of the cam and desktop are working again.
And my config looks like this:
Could it be that the installation of the turn-server are wrong? |
It could be. I'd recommend you follow this guide: https://docs.bigbluebutton.org/2.2/setup-turn-server.html#configure-bigbluebutton-to-use-your-turn-server |
As far as I understand, you are testing against port 3478 here but if you follow the bigbluebutton config, it is not open at all. Only 443 is open, or does it work differently? And then it would also make sense that you, @coderDem get "failed" as output. I see with my turn server, the coturn service crashes irregularly but two times a week and does not restart itself. Since I noticed that, I use my monitoring system to restart the service automatically when it crashes. |
Oh sorry, i was wrong. The default non tls listening port seems to be 3478, also in my config. If i test it from linux with So I would rather guess that your coturn service also crashes from time to time. |
Hello, Thank you for the help guys. I will wait a couple of days and report the results. Thank you and have a great day. |
The part with the restart of the service seems to be very interesting. How do you check if the service crashes? Is the service than not active? |
Yes, the service has "exited" and is inactive. And if this is the case, the monitoring system restarts it. |
@sam9032 I assume you don't use systemd? |
watch out for status |
I use ubuntu 18.04 with systemd, why is it a mess there? How do I enable |
I have a file
Just took a look at systemctl |
Hm interesting. The Do you see any other hints why the coturn service restarts so often? |
@sam9032 I'm running Ubuntu 18 too, but didn't investigate any further. coturn just seems to crash sometimes. I guess, the recommendation for Ubuntu 20 has some serious background. :-) |
Simply adding :3478 in the in-house turn server entry in /usr/share/bbb-web/WEB-INF/classes/spring/turn-stun-servers.xml, like -- Update -- |
I believe it's required to specify the stun port. |
Yes, this is required for stun and should be available. This is also specified in the bigbluebutton documentation. |
The sample config in BBB docs does NOT include the port in the stun section: See https://docs.bigbluebutton.org/admin/setup-turn-server.html#configure-bigbluebutton-to-use-your-turn-server If the port is mandatory (I'm wondering though because I haven't had any problems with that configuration and 3478 is the default port anyway) it should be added to the sample config. |
It is not mandatory, since 3478 is the default port. 443 on the other hand is not the default port for TURN over TLS; that would 5349. That is why this port needs to be specified. |
Hmm, you're right. I was firmly convinced that I read it there along with the port and in my config, it is also set. But since it is the default port, there should be no difference. |
Hello Guys, so this is my lession learend from this TURN-server problem. Answer to my problem: Thank you for the help guys. Best Regards, |
Thank you! Really helpful insights. |
I left the config like in the documentation. |
why was this issue closed? is it fixed? |
Describe the bug
Since the latest Update to version 2.2.28 our users are not able to see or share teir webcams on iOS devices
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When sharing the webcam on iOS it this error should not happen. We expected the same behavior as sharing your webcam on WIN /Linux/ MacOS
**BBB version (optional):2.2.28
BigBlueButton continually evolves. Providing the version/build helps us to pinpoint when an issue was introduced.
Example:
$ sudo bbb-conf --check | grep BigBlueButton
BigBlueButton Server 2.2.2 (1816)
Smartphone (please complete the following information):
Any ideas on that?
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: