# Mediasoup Demo App - Docker

**URL:** <https://mediasoup.discourse.group/t/mediasoup-demo-app-docker/5855>\
**Category:** mediasoup-demo\
**Created:** [February 17, 2024, 9:07pm UTC](https://mediasoup.discourse.group/t/mediasoup-demo-app-docker/5855 "2024-02-17T21:07:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![juber-nunes](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/juber-nunes/32/2531_2.png) [@juber-nunes](https://mediasoup.discourse.group/u/juber-nunes)\
**Post date:** [February 17, 2024, 9:07pm UTC](https://mediasoup.discourse.group/t/mediasoup-demo-app-docker/5855/1 "2024-02-17T21:07:13Z")

</div>

Hi all,

I’m running the docker version of mediasoup-demo, I have done step by step and started the server as a container and running the app against that server. The room opens fine with camera and audio, so I get the invitation link and place on another tab, the same thing happens but “they” cannot see each other the same way it would allow them to see each other once you hit the demo online [https://v3demo.mediasoup.org](https://v3demo.mediasoup.org/). I’m using Chrome and FF but on my local FF doesn’t work at all, always complains about certificate. Chat is also unavailable for whatever reason. Can someone provide some assistance please??

---

<div class="post-metadata">

**Author:** ![juber-nunes](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/juber-nunes/32/2531_2.png) [@juber-nunes](https://mediasoup.discourse.group/u/juber-nunes)\
**Post date:** [February 19, 2024, 10:35pm UTC](https://mediasoup.discourse.group/t/mediasoup-demo-app-docker/5855/2 "2024-02-19T22:35:09Z")

</div>

Just to add a bit more context, I run the server locally as standalone app, it works perfectly. The client app enables video, chat and copying the invitation link to another tab or another browser the “users” can see each other and interact with each other, but running the server on a container doesn’t work the same way. Another thing is that iceState stays at “new” and never moves to “completed” as it does when the server is running as a standalone app loacally.

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [February 19, 2024, 10:41pm UTC](https://mediasoup.discourse.group/t/mediasoup-demo-app-docker/5855/3 "2024-02-19T22:41:29Z")

</div>

Have you read the documentation?

> **[mediasoup :: F.A.Q.](https://mediasoup.org/faq/#running-mediasoup-in-hosts-with-private-ip)**
>
> Cutting Edge WebRTC Video Conferencing

---

<div class="post-metadata">

**Author:** ![juber-nunes](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/juber-nunes/32/2531_2.png) [@juber-nunes](https://mediasoup.discourse.group/u/juber-nunes)\
**Post date:** [February 21, 2024, 6:46pm UTC](https://mediasoup.discourse.group/t/mediasoup-demo-app-docker/5855/4 "2024-02-21T18:46:01Z")

</div>

Thanks for your response @ibc and apologies for my delay. I did read but I was not able to map that to my problem, very sorry. I was also experimenting deploying that on my local kubernetes environment but got the same issue.

 ![image](https://global.discourse-cdn.com/free1/uploads/mediasoup/original/2X/2/2a43320a44b9ba98648412cc6da90dda0793e8d6.jpeg)

---

<div class="post-metadata">

**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\
**Post date:** [February 21, 2024, 7:25pm UTC](https://mediasoup.discourse.group/t/mediasoup-demo-app-docker/5855/5 "2024-02-21T19:25:27Z")

</div>

You have to route the UDP/TCP ports you open in mediasoup from the public ip to the private ip of the mediasoup server.