local web app: recording works via localhost:9000, but not IP_ADDR:9000
See original GitHub issueHello, the web app works nicely when started with docker-compose up
, just by going to http://localhost:9000 and recording. 127.0.0.1 (which is synonym) works okay as well.
However, when I use http://MY_IP_ADDR:9000/en/record (where MY_IP_ADDR is the IP address of my computer in the local network) from my computer, I can browse through the webapp, but when I click the “red button” on http://MY_IP_ADDR:9000/en/record, nothing happens – recording does not start.
Any ideas how to fix this?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
local web app: recording works via localhost:9000, but not ...
Hello, the web app works nicely when started with docker-compose up, just by going to http://localhost:9000 and recording.
Read more >WebApp accessible via localhost but not 127.0.0.1
when someone else from my local network tries to access the app he can do it via my computer name but not via...
Read more >Dev Tip: How to view localhost web apps on your phone
Once you are able to view your app locally on your computer via localhost, you can move to step 2. Step 2: Find...
Read more >web app builder not working in local host - Esri Community
Solved: i make a application with web app builder 2.11 (developer edition).when i run bat file its working but when i download &...
Read more >Local web app not resolving localhost - nginx - Server Fault
There is some discussion out there about this problem. People are saying formatting issues (missing/lack of/incorrect hidden characters) in the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Chrome doesn’t allow getusermedia from untrusted sources, so that’s probably it. Maybe we should add a self signed cert to the docker setup?
On Tue, Jun 26, 2018, 12:39 Zeno Gantner notifications@github.com wrote:
The reported problems were with Chromium. With Firefox 60.0.2 it works.