EricssonResearch / EricssonResearch/openwebrtc
openwebrtc application is not accessible
- Dominant language
- C
- Stars
- 1.8k
- Forks
- 531
- PR merge metrics
- No merged PRs in 30d
Description
I have downloaded the successfully build openwebrtc public image from docker hub and using it. After running the following command 'openwebrtc-daemon', I tried to access the application from the browser with the public_ip:10717 of the AWS EC2 instance. When I check the app to which ports it is listening to using the following command- 'netstat -pan', service openwebrtc-daemon is listening to the following ports 10717,10719 and the ip its listening to is 127.0.0.1. Not able to access the application. What could be the reason behind this?
Contributor guide
Research direction
Start by reproducing the Docker deployment on the AWS EC2 instance, running openwebrtc-daemon and checking netstat -pan for ports 10717 and 10719. Investigate why the service is bound to 127.0.0.1 rather than an externally reachable address. Done means the application can be accessed through the instance's public IP and the listening behavior is documented or corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker
- Domain
- cloud, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100