Skip to content
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

Firefox not working on none lan server (Basic example) #426

Closed
cracker0dks opened this issue Mar 20, 2016 · 20 comments
Closed

Firefox not working on none lan server (Basic example) #426

cracker0dks opened this issue Mar 20, 2016 · 20 comments

Comments

@cracker0dks
Copy link
Contributor

I cant figur out why firefox is not working on the last commit (Basic example).
It works on chrome and on firefox if the server is in the same network (lan).

Online only chrome is working and firefox not. (but firefox console log is the same as on lan)

tested on 3 different servers and 2 different pcs with last firefox and licode version.

Can anyone confirme this?
How can I debug this if the console log is the same?

Thanks :)

@prospdragon
Copy link

I get same issue.
In my case, It worked on Firefox 44, but not working on 45.(of course, it works on chrome.)
In console of firefox, it shows "ICE failed, see about:webrtc for more details"

Is this issue occur only for me, or anyone ?

@cracker0dks
Copy link
Contributor Author

Ok thanks! should be for everyone. Tested this on different pcs with latest firefox and on Firefox nightly.

@prospdragon
Copy link

I fixed this problem.
In my case, it was problem of turn server.
I did re-config of turn server, and licode works well in firefox too.

@cracker0dks
Copy link
Contributor Author

wow. What do you mean by re-config ? change the IP ?

@prospdragon
Copy link

Changed the config of turn server.

@cracker0dks
Copy link
Contributor Author

mmm I use the default turn server (google) maybe I have to switch or just wait? What Turn server do you use?

@prospdragon
Copy link

I'm using rfc5766-turn-server.

@cracker0dks
Copy link
Contributor Author

I tested with and without TURN Server but both not working for me. about:webrtc logs for not working external server on firefox:
image

Log for local Server (working):
image

I got one entry more but no fails... but still no connection. This is the basicExample.

EDIT: I got a lot of: RTCIceServer.url is deprecated! Use urls instead.
warnings in firefox but I think this is not the problem because local server is working

@cracker0dks
Copy link
Contributor Author

Ok I figuered out how I can connect to online server with firefox:

  1. Connect to a room
  2. Wait until: DEBUG: Gathered all candidates for this pc pops up in the console (about 7sec)
  3. Connect to the same room again
    This works for me 90% of the time. Is this maybe a Firefoxbug ?

@cracker0dks
Copy link
Contributor Author

image

Who is using Firefox with that bug? :D

Its still buggy with the last Commit.

Here is the Server log for firefox:

2016-04-18 13:30:14.156  - INFO: RoomController - Adding publisher peer_id  283343756105750800 options { state: 'erizo',
  data: true,
  audio: true,
  video: true,
  minVideoBW: 0 }
2016-04-18 13:30:14.156  - INFO: ECCH - Contacting Agent  ErizoAgent  for a new ErizoJS
2016-04-18 13:30:14.157  - INFO: ErizoAgent - Get erizo JS ba07336c-0330-a560-4d5a-fdaf5d4980e3
2016-04-18 13:30:14.159  - DEBUG: RoomController - ErizoJS id: ba07336c-0330-a560-4d5a-fdaf5d4980e3 assigned for publisher 283343756105750800
2016-04-18 13:30:24.364  - WARN: RoomController - ErizoJS 29a4f9a7-dbab-8dcf-e7dc-c8ff32e9b644 is empty and does not respond, removing

@cracker0dks
Copy link
Contributor Author

Ok with the new FF46 its working on win again (at least win10)
Ubuntu FF still buggy

@mccob
Copy link

mccob commented May 2, 2016

Over months, I see WebRTC calls failures increasing with Firefox...

@cracker0dks
Copy link
Contributor Author

FF 46.0.1 on windows is buggy again... what is mozilla doing :(

@mccob
Copy link

mccob commented May 12, 2016

No problem here with FF 46.0.1 on windows

@cracker0dks
Copy link
Contributor Author

cracker0dks commented May 12, 2016

have you tested over internet? (not local and not on lan)

@mccob
Copy link

mccob commented May 12, 2016

yes over Internet

@cracker0dks
Copy link
Contributor Author

cracker0dks commented May 12, 2016

ok thanks! That gives me hope. with or without TURN server?

@mccob
Copy link

mccob commented May 12, 2016

with TURN

@cracker0dks
Copy link
Contributor Author

cracker0dks commented May 12, 2016

ok, have to try this! thanks :)
Im testing without at the moment

@cracker0dks
Copy link
Contributor Author

TURN not solved this..

Long story short: It is a firefox port problem!

Long story: My firewall only allowed ports:80, 443, 8080 and 30000-30100/UDP I also set MINPORT=30000 and MAXPORT=30100 at the licode_config, but Firefox will not work with this settings (no problem for chrome).

This was not a problem a few firefox versions back -> might be a Firefox bug?!

Here is a work around:
Firefox tries to connect to port 1025 - 65535/UDP for WebRTC. And it seems that Firefox starts at 1025 and stops if it can't connect?!. So if you start at open port 1025 and go to port 1125 everything is working with Firefox.

The best way (for no limits) is to open port: 1025-65535/UDP -> for firefox

@prospdragon & @mccob thanks for your help 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants