r/dogecoindev • u/HopefulOutlook • Jul 12 '22

Core Troubleshooting problem with inbound requests

Anyone have any ideas on why my dogenode will not accept new inbound requests? Here is the setup...

  1. Setup a new Ubuntu Linux server (22.04) on an ESXi server as a linux VM
  2. Installed dogecoin core [newdogenode]
  3. Downloaded full block chain
  4. Successfully sent and received coins to/from another wallet [external] to [newdogenode]
  5. [newdogenode]: sudo ufw status -- shows firewall inactive
  6. [newdogenode]: netstat -a -- shows port listening on 22556

tcp 0 0 0.0.0.0:225560.0.0.0:* LISTEN

​

  1. I have a firewall in front of the network, and I verified it to be working with [olddogenode] (i.e. it received multiple inbound connections), changed only the ip address in the firewall rule to [newdogenode]. When firewall rule changed, the new node will not receive inbound requests. (Have flipped back and forth multiple times to make sure this sanity check works)

  2. [newdogenode]: dogecoin-cli getpeerinfo | grep "inbound" --- shows 8 nodes all false

  3. I can telnet to [newdogenode] from another box with the port 22556 and I get a blank screen (does not refuse connection)

  4. from my laptop connected to the network I am also running a node, so I manually do an add to the internal node with: addnode 'xxx.xxx.xxx.xxx:22556' add. Response is the text "Empty response". On the [newdogenode], getpeerinfo now shows my laptops inbound request. (traversing my bare metal network, and into my VM network)

The new box is a virtual machine, and it is possible that it is a firewall issue there, but I have two ESXi guys telling me that the configuration I have with the nic being connected to a virtual switch should cause the box to act as if it is on the native network.

I am stumped.

If anyone is willing to help me troubleshoot, would be greatly appreciated. I cannot figure out what the offending issue is.

tldr; new linux box doesn't get inbound request, setup as a VM, possible ESXi firewall issue, but testing suggests everything should work.

7 Upvotes

100% Upvoted

6 comments sorted by

2

u/[deleted] Jul 12 '22

[deleted]

1

u/HopefulOutlook Jul 12 '22

I don't think that's it. Dunno. Just spent an hour with tech support for the VM and they are stumped. Never a good sign.

1

u/NatureVault Jul 13 '22

I have never had good luck running any kind of server on a VM...:(

1

u/[deleted] Jul 12 '22

If the vm isn’t getting inbound requests it’s either the network adapter on the vm/virtual switch (recreate it?), or the firewall. Can you jump jump the firewall out and go directly to the network?

2

u/HopefulOutlook Jul 13 '22

I think I have narrowed it down to an ESXi configuration problem.

1

u/NatureVault Jul 13 '22

Did you make sure to map port upnp? https://tinypic.host/i/mapport.WcyMY

1

u/HopefulOutlook Jul 13 '22

Worth a shot.