I am having trouble with calls placed/received from Firefox v27 to Chrome v32
One computer is behind a corporate firewall (Chrome) & the other is on a separate wireless network (Firefox).
Chrome to Chrome calls work flawlessly but when firefox is involved I do not receive the persons video, I get a local preview stream but not the other side.
There are no errors except a warning( [vline.media] Unknown system constraint minbitrate) in the console and VLine believes we are connected I just don't get their stream.
Tried calling through my application , and then just using 2 VLine pages with no success.
How can I go about troubleshooting this?. Known troubles with Firefox?
Firefox doesn't support TCP ICE candidates: https://bugzilla.mozilla.org/show_bug.cgi?id=891551. It's likely that the firewalls involved are blocking UDP, and since Firefox isn't using TCP candidates it's unable to connect.
Related
Nothing too complex with this question, trying to use the chrome devtools protocol in chrome remote interface in order to authenticate with a proxy (headerlessly).
I believe this is already a thing, as the CRI has AuthChallange and AuthChallangeResponse types, as well as puppeteer (high level API around the devtools protocol) already having an authenticate method.
From a small amount of previous experience with the chrome remote interface / chrome devtools protocol, I believe that this problem is likely solved by using Network events in order to listen out for the "AuthChallange" and send / intercept some kind of response.
This is as much as I am aware of so far, and am looking for that simple piece of code which a day of research and googling has unfortunately not provided.
EDIT:
Checked documentation for devtools protocol, but can't find an event that would be related to connecting to a proxy ?
If anymore information is required I can provide this asap
I create a webrtc sample based On this tutorial. this work on my local network fine and I can send and receive signal and videos. but when I connect from internet ti the server and two peer are not in same network video connection does not create.
I am using self sign Certificate and must add them two browsers.
there is no error or exception. my signaling server is a web socket server written in nodejs.
Original Answer
I believe that you require a HTTPS (SSL certificate) if you are using Chrome +47 to be deployed online, but is not required if serving from a local machine on the same network.
According to caniuse; Edge and Firefox may yield non blocking results (but prefix with moz):http://caniuse.com/#feat=stream
The issue isn't necessarily WebRTC but getUserMedia/Stream API isn't provided when the called from a non-secure site (or non-localhost address).
Attached Image:
(https://developers.google.com/web/updates/2015/10/chrome-47-webrtc)
Update:
Did a bit more digging around, and the following answer is related to the question getUserMedia() in chrome 47 without using https i.e. possible duplicate;
You "can" launch a Chrome browser to accept the insecure origin; however, that's temp. fix, whereas you'd probably want to get a certificate.
chrome.exe --user-data-dir=/test/only/profile/dir --unsafely-treat-insecure-origin-as-secure="http://example.com"
Feeling a bit lost after many days of relentless digging and looking for inspiration...
The story so far:-
I have a Microchip PIC32-based wifi-dev board running TCP/IP stack v5.36.
After boot-up, the app works fine when requesting the default 'mchp.local' domain name in the browser. The web browser receives updates correctly every second from the embedded web server on the PIC.
After an indeterminate time however (usually about 1 hour or so), the 'mchp.local' page times out and the browser reports
'ERR_NAME_NOT_RESOLVED: The server at mchp.local cannot be found. because the DNS lookup failed.'
And yet, I can access the app on its corresponding IP address (in this case 172.16.15.103) and I see the app is running fine.
I also see infinite loop in the the main() routine is running as expected and the web server is responding to changes when I request pages using just the IP address.
I have tested using Chrome on Windows and Mac machines - same issue.
I have tried using Packet Peeper (a free network packet analyser for Mac OS X) to filter out all messages NOT on UDP port 5353 (as per RFC 6762) and I see nothing useful.
I have trace-debugged the code and found that the mDNS state machine is in DEFEND mode, both before and after the moment when the app stops responding with DNS "ERR_NAME_NOT_RESOLVED".
I suspect the problem lies in the multicast DNS module but my findings so far do not help me to piin point the root cause.
Any clues? Where should I look next?
My environment:
Mac OS X 10.9.5 (Mavericks)
Browser: Chrome v.44
Embedded Kit uC: Microchip PIC32MX695F512H
Embedded Kit WiFi interface: Microchip MRF24WB0MA
Dev Tools: PICKit3, MPLAB X IDE v2.25, Packet Peeper 2014-06-15
Is it possible to initiate a TCP connection from a browser?
If so, does there already exist browser (esp. Firefox and Chrome) extensions that do this? If no extensions exist yet, do you know the core elements/functions to create a Firefox/Chrome browser-initiated TCP connection?
The Chrome Browser (I think since v24 in the stable channel) lets you host a TCP server, and the samples indicate that it can connect to a telnet server, which means that it is also capable of being a TCP client.
https://github.com/GoogleChrome/chrome-app-samples/tree/master/tcpserver
https://github.com/GoogleChrome/chrome-app-samples/tree/master/telnet
But these are not standardized, so, if you can work with websockets, do prefer that.
http://developer.chrome.com/apps/socket.html
There are Websockets, but they are limited to the websocket protocol outlined at in RFC 6455.
So far, most modern webbrowsers support it
I'm using Socket.IO on Node.js.
The Example here: http://socket.io/#how-to-use
First Example.
I have tested on my computer, it works great. ( Installed on VPS, connect by IP. not localhost )
But the problem is, my friends, they visit the page:
http://112.78.8.221:8085/
Press F12 for debug , under Console, they show not thing.
But in my browser console ( Chrome, Firefox ) , I see a object return.
On debug of my friend:
I see :
jsonppolling closed due to exceeded duration
setting request GET /socket.io/1/jsonp-polling/blablabalblabal
Setting poll timeout
discatding transport and same as xhr-polling, timeout and discard.
So, both of us used latest version of Chrome and FF, can u guys help on this one? a week with this problem already :(
I believe there is something strange going on with his network. Maybe he is going through a proxy connection or something? I was able to hit your service and got an object back without a problem. Some offices and universities will also block ports other than the common 80, 443, 22, etc. If you can, try hosting on a lower port number, or if possible on port 80 to eliminate that as a cause of the problem.