Node-RED Dashboard on Website

[jmlResults]

Need a bit of IT help please. I am trying to share one of my dashboards on my wordpress website that is being hosted externally by Digital Oceans. I've opened port 1880 to my pi at internal address 192.168.1.100. On my website I used my external IP 64.64.***.**:1880/ui/#/0 which works fine when I access my website from outside of my home network. From inside my home network I get "refused to connect" . Is there a work around that I can work on my site and see my Dashboards from inside my home network? 

Hope that makes sense :). 

Now that I have port 1880 open for Node_red and port 80 for emoncms I need to secure my PI...any advice / direction for best options ?  

[Ben Hardill]

This entirely depends on your router, but you need to look for something called loopback NAT or hairpin networking

[jmlResults]

Thanks Ben, 

My router is a Western Digital N900...google says it supports loopback but examples or how to is sparse ? Is it complex to setup and maintain ? 

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/rq_qqblyCq4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/fe3e8ec5-cbb1-4ad2-a0b4-f9a1f2284acf%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Julian Knight]

The easiest way to fix this is to access via domain name rather than IP Address. Then you can easily define a local mapping for the name. Of course, to do that, you need a domain name. but it only costs a few dollars a year.

On Wednesday, 11 January 2017 00:07:32 UTC, jmlResults wrote:

Thanks Ben, 

My router is a Western Digital N900...google says it supports loopback but examples or how to is sparse ? Is it complex to setup and maintain ? 

On Tue, Jan 10, 2017 at 6:51 PM, Ben Hardill <b.ha...@gmail.com> wrote:

This entirely depends on your router, but you need to look for something called loopback NAT or hairpin networking

On Tuesday, 10 January 2017 23:43:32 UTC, jmlResults wrote:

Need a bit of IT help please. I am trying to share one of my dashboards on my wordpress website that is being hosted externally by Digital Oceans. I've opened port 1880 to my pi at internal address 192.168.1.100. On my website I used my external IP 64.64.***.**:1880/ui/#/0 which works fine when I access my website from outside of my home network. From inside my home network I get "refused to connect" . Is there a work around that I can work on my site and see my Dashboards from inside my home network? 

Hope that makes sense :). 

Now that I have port 1880 open for Node_red and port 80 for emoncms I need to secure my PI...any advice / direction for best options ?  

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/rq_qqblyCq4/unsubscribe.

To unsubscribe from this group and all its topics, send an email to node-red+u...@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

[Jeff Lamer]

Hey Julian, 

To be clear, if I purchase a domain name I link it to my " static external IP" ? this will remedy my loopback issue ?  

Jeff 

[Colin Law]

I am not convinced that will sort it, but you don't need to buy a name
to try it. You can get yourself a free name from, various places. I
use duckdns.org.

Colin

> You received this message because you are subscribed to the Google Groups
> "Node-RED" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to node-red+u...@googlegroups.com.
> To post to this group, send email to node...@googlegroups.com.
> Visit this group at https://groups.google.com/group/node-red.
> To view this discussion on the web, visit

> https://groups.google.com/d/msgid/node-red/4aa17e87-9e52-4783-9bec-a85d5aafde7f%40googlegroups.com.

[Julian Knight]

The external domain name is part of the solution. The other part is to get your internal machines to both recognise the name and direct it to the internal address rather than the external one.

This can be done several ways.

Some routers are clever enough to be able to do this automatically, recognising that a network address translation rule that directs the incoming WAN request to the internal address should be matched by an internal route.

Otherwise, the simplest thing to do is to manually add the name and internal address to your HOSTS file. Though don't forget to remove it if you are using a laptop that may need to access it both outside and in.

[Colin Law]

There is also the question of why it matters that, when in the local
network, trying to access the external ip address does not work. Just
use the internal one instead.

Colin

> https://groups.google.com/d/msgid/node-red/52e38000-62cb-4a25-a376-a68ff895fec6%40googlegroups.com.

[jmlResults]

Hi Collin, 

The only reason it matters is per my first post. I am playing with embedding things into my website which is hosted externally. When I test my pages from inside my network I can't see the dashboards from Node -Red or Emoncms on my website. Externally it is fine....just makes it tough to setup/configure how the layout looks on the webpage. 

> email to node-red+unsubscribe@googlegroups.com.

> To post to this group, send email to node...@googlegroups.com.
> Visit this group at https://groups.google.com/group/node-red.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/node-red/52e38000-62cb-4a25-a376-a68ff895fec6%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

--
http://nodered.org

Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/rq_qqblyCq4/unsubscribe.

To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send an email to node...@googlegroups.com.

Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAL%3D0gLsTjp5Jb5AE6D3UFurAZkjO7RC-CKiEqPZcpfa5-BpTrQ%40mail.gmail.com.

[Colin Law]

OK, understood.

Firstly check that your router has the latest version of its software,
if you have not already done so.

If that doesn't help then I can see two options. The first is to get a
router that works. The second is to follow Julian's suggestion. Get
yourself a domain name from (for example duckdns),
jmlresults.duckdns.org for example, or buy one for yourself. This
will be a good thing anyway as it is not a good idea to have ip
addresses referenced directly in your website, it will be hard work if
you ever change your address. Then edit the file /etc/hosts and add to
it a line to direct that address to the internal network, something
like
192.168.xxx.xxx jmlresults.duckdns.org
That will send references to that domain to the internal address
instead of looking it up on the internet.

Colin

>> > email to node-red+u...@googlegroups.com.

>> > To post to this group, send email to node...@googlegroups.com.
>> > Visit this group at https://groups.google.com/group/node-red.
>> > To view this discussion on the web, visit
>> >

>> > https://groups.google.com/d/msgid/node-red/52e38000-62cb-4a25-a376-a68ff895fec6%40googlegroups.com.
>> >
>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> http://nodered.org
>>
>> Join us on Slack to continue the conversation: http://nodered.org/slack
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Node-RED" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/node-red/rq_qqblyCq4/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to

>> node-red+u...@googlegroups.com.

>> To post to this group, send an email to node...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/node-red.
>> To view this discussion on the web, visit
>> https://groups.google.com/d/msgid/node-red/CAL%3D0gLsTjp5Jb5AE6D3UFurAZkjO7RC-CKiEqPZcpfa5-BpTrQ%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>

> --
> http://nodered.org
>
> Join us on Slack to continue the conversation: http://nodered.org/slack
> ---
> You received this message because you are subscribed to the Google Groups
> "Node-RED" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to node-red+u...@googlegroups.com.
> To post to this group, send email to node...@googlegroups.com.
> Visit this group at https://groups.google.com/group/node-red.
> To view this discussion on the web, visit

> https://groups.google.com/d/msgid/node-red/CA%2BzxUUsRwWciDkjQPrXJp2Abi6gYiTJ1Sco5Syx3dwpFc1gFng%40mail.gmail.com.