Score:0

Unable to acess my services using public ip address

in flag

I am running Ubuntu 20.04.3 LTS 64-bit

My local network IP has been DMZ and the port i'm looking to use is forwarded.

when I start my NodeJS process, it is listening on ip 0.0.0.0 on the selected port.

By runnning sudo netstat -tulpn I get the confirmation.

> tcp     0    0 0.0.0.0:9998       0.0.0.0:*        LISTEN    11480/node

Now when I run ifconfig I get this output

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:ccff:fe54:2b38  prefixlen 64  scopeid 0x20<link>
        ether 02:42:cc:54:2b:38  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12  bytes 1476 (1.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.11  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fe80::ec9:aa20:4d70:8eff  prefixlen 64  scopeid 0x20<link>
        ether 04:d9:f5:7d:8a:ff  txqueuelen 1000  (Ethernet)
        RX packets 142036  bytes 138928770 (138.9 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 114221  bytes 26927463 (26.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xb2500000-b2520000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 11534  bytes 7936309 (7.9 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 11534  bytes 7936309 (7.9 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

If I reach any of these addresses from my PC I get a response back.

But if I try to reach my public IP, I get no response.

I'm not sure what could be missing. The router is forwarding the port to 192.168.2.11

I am listening on 0.0.0.0 which should be all networks. I also have the rule in the firewall, if I run sudo ufw status

I get;

Status: active

To                         Action      From
--                         ------      ----
9998                       ALLOW       Anywhere                  
9998 (v6)                  ALLOW       Anywhere (v6) 

Would docker have anything to do with it? I'm not starting the app in a container yet since. I start the node process as the user logged in from the terminal plain and simple.

The sudo lshw -C network returns

*-network                 
       description: Ethernet interface
       product: Ethernet Connection (7) I219-V
       vendor: Intel Corporation
       physical id: 1f.6
       bus info: pci@0000:00:1f.6
       logical name: eno1
       version: 10
       serial: 04:d9:f5:7d:8a:ff
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=5.11.0-38-generic duplex=full firmware=0.5-4 ip=192.168.2.11 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:130 memory:b2500000-b251ffff

I will add any input required to get this to work. Just ask for it. Thank you for your time!

Doug Smythies avatar
gn flag
It is very common to not be able to reach your own public IP from within your own local area network (LAN). It depends on your router.
in flag
@DougSmythies Dang you right! just went trough with my phone
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.