# Expose node red to internet without open port forwading

**URL:** <https://discourse.nodered.org/t/expose-node-red-to-internet-without-open-port-forwading/9358>\
**Category:** General\
**Created:** [24 March 2019 06:41 UTC](https://discourse.nodered.org/t/expose-node-red-to-internet-without-open-port-forwading/9358 "2019-03-24T06:41:36Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Andrei](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/andrei/32/10446_2.png) [@Andrei](https://discourse.nodered.org/u/Andrei)\
**Post date:** [24 March 2019 21:15 UTC](https://discourse.nodered.org/t/expose-node-red-to-internet-without-open-port-forwading/9358/4 "2019-03-24T21:15:45Z")

</div>

another alternative, not mentioned in previous posts and links: webhookrelay

> [@\[ANNOUNCE\] node-red-contrib-webhookrelay](https://discourse.nodered.org/t/announce-node-red-contrib-webhookrelay/5989):
>
> Hello, I am creator of [Webhook Relay](https://webhookrelay.com) and a big fan of Node-RED. I would like to present a general purpose webhook receiving node node-red-contrib-webhookrelay which can help you receive & process webhooks from 3rd party providers such as Google Home actions, GitHub, Gitlab and so on without having a public IP/domain or configuring NAT/firewall. The only requirement is an internet connection. How it works Node node-red-contrib-webhookrelay works by creating a websocket to [webhookrelay.com](http://webhookrelay.com) public…

---

_[View the full topic](https://discourse.nodered.org/t/expose-node-red-to-internet-without-open-port-forwading/9358)._
