# Oracle Cloud problem ¨- SOLVED

**URL:** <https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340>\
**Category:** General\
**Created:** [5 August 2023 20:21 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340 "2023-08-05T20:21:45Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![jiripaskov](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jiripaskov/32/81776_2.png) [@jiripaskov](https://discourse.nodered.org/u/jiripaskov)\
**Post date:** [5 August 2023 20:21 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340/1 "2023-08-05T20:21:45Z")

</div>

Hello. I used this manual to install Nodered [https://blogs.oracle.com/developers/post/installing-node-red-in-an-always-free-vm-on-oracle-cloud](https://blogs.oracle.com/developers/post/installing-node-red-in-an-always-free-vm-on-oracle-cloud).

Port 1880 **is opened** from internet on my public IP.  
sudo firewall-cmd --list-all shows **ports: 1880/tcp** : node-red 1482 nodered 19u IPv4 32622 0t0 TCP \*:1880 (LISTEN)  
nodered **started** and listening on 1880

but there is nothing on [http://my-public-ip:1880](http://my-public-ip:1880)

Any idea where to start? Thanks

---

<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:** [5 August 2023 20:53 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340/2 "2023-08-05T20:53:38Z")

</div>

Show us the startup log please (as a result of running `node-red-stop` then `node-red-start`. Copy/paste the text please, not screenshot.

I think there is a bit of a flaw in the tutorial, as if you do manage to open your node-red to the internet there is a good chance it will get hacked within minutes (or at least hours). Perhaps that has happened already.

Can you ping your ip?

---

<div class="post-metadata">

**Author:** ![jiripaskov](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jiripaskov/32/81776_2.png) [@jiripaskov](https://discourse.nodered.org/u/jiripaskov)\
**Post date:** [6 August 2023 07:36 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340/4 "2023-08-06T07:36:27Z")

</div>

Regarding to ping - Yes, as I opened ICMP in security list (in Oracle CLoud) I can PING now.  
Here is node-red-stop:

```auto
[opc@instance-20230805-1252 ~]$ node-red-stop
Stop Node-RED

Use node-red-start to start Node-RED again

```

Here is node-red-start:

```auto
Start Node-RED

Once Node-RED has started, point a browser at http://10.0.0.33:1880
On Pi Node-RED works better with the Firefox or Chrome browser

Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot

To find more nodes and example flows - go to http://flows.nodered.org
6 Aug 07:36:04 - [info]

Welcome to Node-RED
===================

6 Aug 07:36:04 - [info] Node-RED version: v3.0.2
6 Aug 07:36:04 - [info] Node.js version: v14.21.3
6 Aug 07:36:04 - [info] Linux 5.15.0-102.110.5.1.el8uek.aarch64 arm64 LE
6 Aug 07:36:04 - [info] Loading palette nodes
6 Aug 07:36:04 - [info] Settings file : /home/opc/.node-red/settings.js
6 Aug 07:36:04 - [info] Context store : 'default' [module=memory]
6 Aug 07:36:04 - [info] User directory : /home/opc/.node-red
6 Aug 07:36:04 - [warn] Projects disabled : editorTheme.projects.enabled=false
6 Aug 07:36:04 - [info] Flows file : /home/opc/.node-red/flows.json
6 Aug 07:36:04 - [info] Creating new flow file
6 Aug 07:36:04 - [warn] Encrypted credentials not found
6 Aug 07:36:04 - [info] Server now running at http://127.0.0.1:1880/
6 Aug 07:36:04 - [info] Starting flows
6 Aug 07:36:04 - [info] Started flows

```

---

<div class="post-metadata">

**Author:** ![jiripaskov](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jiripaskov/32/81776_2.png) [@jiripaskov](https://discourse.nodered.org/u/jiripaskov)\
**Post date:** [6 August 2023 07:38 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340/5 "2023-08-06T07:38:52Z")

</div>

Here are ingress/egress rules from Oracle Cloud:

 ![dd864f38-3c11-4068-ac7b-2c711d5edd2a](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/6/463b46d3840b6efa49f7e4ec67a333cd691ae9c2.png)  
 ![0258aa87-2ba5-4c7b-b3e0-4c3493d28380](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/3/63a68a0f6c54a4fc72f7e2f9d6ffcceefb904b50.png)

---

<div class="post-metadata">

**Author:** ![jiripaskov](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jiripaskov/32/81776_2.png) [@jiripaskov](https://discourse.nodered.org/u/jiripaskov)\
**Post date:** [6 August 2023 07:44 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340/6 "2023-08-06T07:44:11Z")

</div>

After reboot (nodered set as service) it shows:

```auto
[opc@instance-20230805-1252 ~]$ sudo lsof -i -P -n | grep LISTEN
systemd 1 root 37u IPv4 23897 0t0 TCP *:111 (LISTEN)
systemd 1 root 39u IPv6 23899 0t0 TCP *:111 (LISTEN)
rpcbind 1435 rpc 4u IPv4 23897 0t0 TCP *:111 (LISTEN)
rpcbind 1435 rpc 6u IPv6 23899 0t0 TCP *:111 (LISTEN)
node-red 1482 nodered 18u IPv4 32387 0t0 TCP *:1880 (LISTEN)
sshd 2144 root 3u IPv4 32475 0t0 TCP *:22 (LISTEN)
sshd 2144 root 4u IPv6 32477 0t0 TCP *:22 (LISTEN)
pmcd 2327 pcp 0u IPv4 33484 0t0 TCP 127.0.0.1:44321 (LISTEN)
pmcd 2327 pcp 3u IPv6 33485 0t0 TCP [::1]:44321 (LISTEN)
pmlogger 3119 pcp 7u IPv4 35574 0t0 TCP 127.0.0.1:4330 (LISTEN)
pmlogger 3119 pcp 8u IPv6 35575 0t0 TCP [::1]:4330 (LISTEN)
osms-agen 3279 root 7u IPv6 38624 0t0 TCP 127.0.0.1:32768 (LISTEN)
osms-agen 3279 root 10u IPv4 38652 0t0 TCP 127.0.0.1:9003 (LISTEN)
[opc@instance-20230805-1252 ~]$

```

---

<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:** [6 August 2023 07:52 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340/7 "2023-08-06T07:52:45Z")

</div>

> [@jiripaskov](#):
>
> sudo firewall-cmd --list-all shows **ports: 1880/tcp** : node-red 1482 nodered 19u IPv4 32622 0t0 TCP \*:1880 (LISTEN)

What does the 1482 there mean?

Have you tried IP:1482?

---

<div class="post-metadata">

**Author:** ![jiripaskov](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jiripaskov/32/81776_2.png) [@jiripaskov](https://discourse.nodered.org/u/jiripaskov)\
**Post date:** [6 August 2023 07:55 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340/8 "2023-08-06T07:55:27Z")

</div>

I think 1482 (second column) is process id? Not sure.

---

<div class="post-metadata">

**Author:** ![jiripaskov](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jiripaskov/32/81776_2.png) [@jiripaskov](https://discourse.nodered.org/u/jiripaskov)\
**Post date:** [6 August 2023 07:57 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340/9 "2023-08-06T07:57:08Z")

</div>

Strange. Using this command there is nothing listening on 1880 p ort:

```auto

[opc@instance-20230805-1252 ~]$ sudo netstat -tulpn | grep LISTEN
tcp 0 0 127.0.0.1:9003 0.0.0.0:* LISTEN 3279/osms-agent
tcp 0 0 127.0.0.1:4330 0.0.0.0:* LISTEN 3119/pmlogger
tcp 0 0 0.0.0.0:1880 0.0.0.0:* LISTEN 1482/node-red
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2144/sshd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/systemd
tcp 0 0 127.0.0.1:44321 0.0.0.0:* LISTEN 2327/pmcd
tcp6 0 0 127.0.0.1:32768 :::* LISTEN 3279/osms-agent
tcp6 0 0 ::1:4330 :::* LISTEN 3119/pmlogger
tcp6 0 0 ::1:44321 :::* LISTEN 2327/pmcd
tcp6 0 0 :::22 :::* LISTEN 2144/sshd
tcp6 0 0 :::111 :::* LISTEN 1/systemd

```

---

<div class="post-metadata">

**Author:** ![jiripaskov](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jiripaskov/32/81776_2.png) [@jiripaskov](https://discourse.nodered.org/u/jiripaskov)\
**Post date:** [6 August 2023 07:57 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340/10 "2023-08-06T07:57:40Z")

</div>

SOrry there is Nodered on 1880.... so problem must be somewghere between VM and internet?

---

<div class="post-metadata">

**Author:** ![jiripaskov](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jiripaskov/32/81776_2.png) [@jiripaskov](https://discourse.nodered.org/u/jiripaskov)\
**Post date:** [6 August 2023 08:02 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340/11 "2023-08-06T08:02:13Z")

</div>

**SORRY.** Seems like it is running OK and problem is with my browser or internet connection. Thank you very much.

---

<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:** [6 August 2023 08:14 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340/12 "2023-08-06T08:14:21Z")

</div>

> [@jiripaskov](#):
>
> I think 1482 (second column) is process id?

Yes, I think you are right.

---

<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:** [20 August 2023 08:14 UTC](https://discourse.nodered.org/t/oracle-cloud-problem-solved/80340/13 "2023-08-20T08:14:56Z")

</div>

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