# Unable to reach https://nodered.org/

**URL:** <https://discourse.nodered.org/t/unable-to-reach-https-nodered-org/64946>\
**Category:** General\
**Created:** [11 July 2022 13:24 UTC](https://discourse.nodered.org/t/unable-to-reach-https-nodered-org/64946 "2022-07-11T13:24:38Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neal](https://avatars.discourse-cdn.com/v4/letter/n/49beb7/32.png) [@Neal](https://discourse.nodered.org/u/Neal)\
**Post date:** [11 July 2022 13:24 UTC](https://discourse.nodered.org/t/unable-to-reach-https-nodered-org/64946/1 "2022-07-11T13:24:38Z")

</div>

Hello Folks,

We have one server at our organization that cannot reach [nodered.org](http://nodered.org). Other machines like user desktops have no issue. Is it possible that the external IP of that server is blocked? Who can I contact to confirm?

Thanks,  
Neal

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [11 July 2022 13:37 UTC](https://discourse.nodered.org/t/unable-to-reach-https-nodered-org/64946/2 "2022-07-11T13:37:02Z")

</div>

> [@Neal](#):
>
> Is it possible that the external IP of that server is blocked

Not likely.

Can this "server" actually contact the internet?

What happens if you ping some known IPs like `ping 8.8.8.8` or `ping 185.199.111.153` from a command prompt on the server?

---

<div class="post-metadata">

**Author:** ![Neal](https://avatars.discourse-cdn.com/v4/letter/n/49beb7/32.png) [@Neal](https://discourse.nodered.org/u/Neal)\
**Post date:** [11 July 2022 13:59 UTC](https://discourse.nodered.org/t/unable-to-reach-https-nodered-org/64946/3 "2022-07-11T13:59:04Z")

</div>

Yes, it can go to other sites. Can even go to [https://flows.nodered.org/](https://flows.nodered.org/)  
I can't actually ping as ICMP is blocked at the firewall. I was just asking the "blocking question" on behalf of our firewall fella's who are stumped at the moment. [nodred.org](http://nodred.org) responds with a connection reset error.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [11 July 2022 14:06 UTC](https://discourse.nodered.org/t/unable-to-reach-https-nodered-org/64946/4 "2022-07-11T14:06:50Z")

</div>

Just to be absolutely clear, node-red (the backend running on the server) only needs access to `npm` for installing nodes - that is all.

The browser where you manage the palette only requires access to the flows library (for showing you what is available)

I thought it important to make this distinction (sorry if you are already aware)

* * *

PS, instead of ping, you can make tests on the server using `wget` or `curl` to test access to npm

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [11 July 2022 14:17 UTC](https://discourse.nodered.org/t/unable-to-reach-https-nodered-org/64946/5 "2022-07-11T14:17:14Z")

</div>

> [@Neal](#):
>
> Is it possible that the external IP of that server is blocked?

If you have multiple servers/PCs on the same network, connected to the internet, then externally they will all have the same IP address. If [nodered.org](http://nodered.org) was blocking the IP then all servers on your network would be blocked.

If the server is on a different local network to the others then try connecting something else to that network and see how it does.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [11 July 2022 14:34 UTC](https://discourse.nodered.org/t/unable-to-reach-https-nodered-org/64946/6 "2022-07-11T14:34:58Z")

</div>

Hi @Neal

We use GitHub Pages to host the site at [nodered.org](http://nodered.org), with CloudFlare handling DNS in front of it.

We don't have any means to block individual IPs like that. So it's hard to suggest anything on our side that could be causing this problem.

---

<div class="post-metadata">

**Author:** ![Neal](https://avatars.discourse-cdn.com/v4/letter/n/49beb7/32.png) [@Neal](https://discourse.nodered.org/u/Neal)\
**Post date:** [11 July 2022 14:36 UTC](https://discourse.nodered.org/t/unable-to-reach-https-nodered-org/64946/7 "2022-07-11T14:36:57Z")

</div>

Thanks! I'll pass that on to our network folks.

Neal

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [9 September 2022 14:37 UTC](https://discourse.nodered.org/t/unable-to-reach-https-nodered-org/64946/8 "2022-09-09T14:37:26Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.