# Cannot access when run in docker

**URL:** <https://discourse.lynckia.com/t/cannot-access-when-run-in-docker/547>\
**Category:** Uncategorized\
**Created:** [July 27, 2017, 3:24pm UTC](https://discourse.lynckia.com/t/cannot-access-when-run-in-docker/547 "2017-07-27T15:24:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Cracker\_F](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/cracker_f/32/137_2.png) [@Cracker\_F](https://discourse.lynckia.com/u/Cracker_F)\
**Post date:** [July 28, 2017, 4:20pm UTC](https://discourse.lynckia.com/t/cannot-access-when-run-in-docker/547/2 "2017-07-28T16:20:12Z")

</div>

yep! basicExample is listening on port 3004 not 3000. You have to add it to the start parameter. Also you need to enable SSL at the config to work without a reverse proxy.

You can take a look at: [https://hub.docker.com/r/rofl256/ezlicode/](https://hub.docker.com/r/rofl256/ezlicode/) I made this slightly changed image to run licode without this pain 🙂

PS: I made this a few hours ago while thinking over a prototype for your other thread: [Freelancer to create video chat application required](http://discourse.lynckia.com/t/freelancer-to-create-video-chat-application-required/545) But I had not much time today to do more than creating the basic container^^

---

_[View the full topic](https://discourse.lynckia.com/t/cannot-access-when-run-in-docker/547)._