I have an application (writen in React.js) that works perfectly in Chrome Browser on my computer.
When I try to load the app on my phone with Chrome, the app loads well when I am in Wifi but not when I am in my mobile network (4G).
I have a perfectly valid SSL certificate created with Let's Encrypt.
Do you have an idea why ?
Did you try to use google chrome dev tool with 3G etc...
Please see the article : https://developers.google.com/web/tools/chrome-devtools/network
Related
I want to test my airconsole game on a smartphone before publishing. The problem is, I can't connect it to the simulator.
If i try to connect (Chrome on Android) it says connecting, after a few seconds it shows the enter code screen but no input is possible. After about 30 seconds I get the message download the app for next time. (Screenshots attached)
Do you know where the problem is?
My files are hosted on a webserver, accessible from everywhere.
Kind regards
Make sure your screen.html and controller.html are accessible from all devices.
Let's assume you are running your local web server on http://192.168.0.2:8080/
Try to access http://192.168.0.2:8080/screen.html and http://192.168.0.2:8080/controller.html using a normal web browser on the device that doesn't work. It should display the screen/controller html.
If you can't access http://192.168.0.2:8080/controller.html from your phone, but from your computer, make sure you are in the same network and that your router does not have "Client Isolation" activated.
If you are testing with real smartphones, make sure you do not use http://localhost/ or http://127.0.0.1/, because localhost is not your computer on the phone but the phone itself!
If you are still unable to connect your phone, you can use the ngrok tool to forward your local url. See our Ngrok Unity Guide for how to do this in the Unity Engine: https://developers.airconsole.com/#!/guides/unity-ngrok
my app is based on ionic framework(ionic3). in all browser, it's working but in safari browser, it's not working (safari browser installed in windows os but other URL working in safari except localhost.
I am using the the pubnub example, but when I am calling with laptop chrome browser to iphone safari browser it's not working.
When I try with Iphone safari browser to laptop Chrome browser then it's working fine.
Can anyone suggest me the solution for this issue?
I'm making a web app that uses WebRTC but it requires https. Is there any way to turn off SSL check on Chrome and Firefox for localhost only or is there any way to make use of WebRTC without https? Thanks.
Chrome has chrome://flags/#allow-insecure-localhost which will ignore certificate errors on localhost. This makes development much easier.
As #vcsjones said
Both Chrome and Firefox treat localhost as a secure context, so localhost should have access to secure context only features like webcam, geolocation, and WebRTC.
It is correct. However, Firefox changed (since Firefox 42) mozSrcObject to srcObject. I changed it to that and it worked.
Since chrome://flags/#allow-insecure-localhost feature is removed from Chrome 88 disable security settings completely helped me to send requests from localhost to server.
Google Security Settings
The way to continue and access the server will be by clicking on an empty location at the background with the browser's error page and type:
thisisunsafe
Chrome supports WebRTC.
But openwebrtc I am not able to run
http://demo.openwebrtc.org:38080/
while apprtc I am able to run
https://apprtc.appspot.com/
so why this problem ?
so what is the difference between openwebrtc and apprtc ?
is there any different implementation in these ?
I know both use WebRTC APIs
so my gut feeling is the demo sample that I use for openwebrtc is not https so chrome doesn’t let it access camera ,mike and so its not working.While Apprtc sample is https
Open web console:
getUserMedia() no longer works on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.
This is a limitation in Chrome. The page works fine in, say, Firefox.