# Node-client: GetSession Fails in production for custom dockerized app (Bug?)

**URL:** <https://openvidu.discourse.group/t/node-client-getsession-fails-in-production-for-custom-dockerized-app-bug/1155>\
**Category:** Issues with deployment\
**Tags:** v2\
**Created:** [June 11, 2020, 10:00am UTC](https://openvidu.discourse.group/t/node-client-getsession-fails-in-production-for-custom-dockerized-app-bug/1155 "2020-06-11T10:00:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pabloFuente](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/pablofuente/32/2536_2.png) [@pabloFuente](https://openvidu.discourse.group/u/pabloFuente)\
**Post date:** [June 11, 2020, 10:34am UTC](https://openvidu.discourse.group/t/node-client-getsession-fails-in-production-for-custom-dockerized-app-bug/1155/2 "2020-06-11T10:34:41Z")

</div>

Hi,

This is clearly a limitation in openvidu-node-client. We’ll update the library to be able to force plain HTTP for use cases as yours.  
For now you can simply change the URL used by your Node app to connect to your OpenVidu Server to https://SERVER\_PUBLIC\_IP/

So, even the app is running in the same host as OpenVidu Server, it will simply use the public secure IP to throw REST petitions to it. This way it will work just fine. But again, we will be updating openvidu-node-client to allow using plain HTTP as OpenVidu endpoint.

Regards.

---

_[View the full topic](https://openvidu.discourse.group/t/node-client-getsession-fails-in-production-for-custom-dockerized-app-bug/1155)._