Topic: [SOLVED] Problem installing Litecoin Listening Full Node (Read 118 times)

Good to see that the problem has been sorted and feel free to post in future if you face any such problems. I am sure the community will be glad to help you. In case you still want to know, Electrum-LTC users can connect to your node randomly if it is available for them in their network. Have a great time!

yes I am also aware about these news, the users are facing isuess while installing the litcoin and they are also very unsatisfied because of these, now I can only ensure you that the authority are trying their best to slove this issues as soon as possible

give information

root@Bitcoin-1:~# ~/litecoin-0.16.0/bin/litecoin-cli getpeerinfo | grep 9333

"addr": "38.87.54.164:9333",
"addr": "174.138.13.27:9333",
"addr": "173.94.177.224:9333",
"addr": "173.255.204.124:9333",
"addrbind": "140.82.58.152:9333",
"addr": "47.97.215.104:9333",
"addrlocal": "127.0.0.1:9333",
"addrbind": "140.82.58.152:9333",
"addrbind": "140.82.58.152:9333",
"addr": "5.9.5.135:9333",
"addrlocal": "127.0.0.1:9333",
"addrbind": "140.82.58.152:9333",
"addrlocal": "127.0.0.1:9333",
"addrbind": "140.82.58.152:9333",
"addrlocal": "127.0.0.1:9333",
"addrbind": "140.82.58.152:9333",
"addrlocal": "140.82.58.152:9333",
"addrbind": "140.82.58.152:9333",
"addrlocal": "127.0.0.1:9333",
"addrbind": "140.82.58.152:9333",
"addrlocal": "127.0.0.1:9333",
"addrbind": "140.82.58.152:9333",
"addrlocal": "140.82.58.152:9333",
"addrbind": "140.82.58.152:9333",
"addrlocal": "127.0.0.1:9333",
"addrbind": "140.82.58.152:9333",
"addrbind": "140.82.58.152:9333",
"addrlocal": "140.82.58.152:9333",
"addrbind": "140.82.58.152:9333",
"addr": "5.39.174.116:9333",
"addr": "94.130.52.104:9333",
"addrbind": "140.82.58.152:9333",

root@Bitcoin-1:~# ~/litecoin-0.16.0/bin/litecoin-cli getblockcount

1464192

root@Bitcoin-1:~# ~/litecoin-0.16.0/bin/litecoin-cli --version

Litecoin Core RPC client version v0.16.0

----

So latest version of Litecoin Core Full Node is running, but it is not listening.

The problem is: My node is invisible from outside on TCP port 9333:

root@thc-1:~# nmap 140.82.58.152
Starting Nmap 7.01 ( https://nmap.org ) at 2018-07-27 23:43 UTC
Nmap scan report for 140.82.58.152.vultr.com (140.82.58.152)
Host is up (0.043s latency).
Not shown: 996 closed ports
PORT STATE SERVICE
22/tcp open ssh
8333/tcp open bitcoin
9998/tcp open distinct32
9999/tcp open abyss
Nmap done: 1 IP address (1 host up) scanned in 2.71 seconds

--- (same test but locally; TCP port 9333 is indeed closed.)

root@Bitcoin-1:~# nmap localhost
Starting Nmap 7.60 ( https://nmap.org ) at 2018-07-27 23:44 UTC
Nmap scan report for localhost (127.0.0.1)
Host is up (0.0000040s latency).
Other addresses for localhost (not scanned): ::1
Not shown: 996 closed ports
PORT STATE SERVICE
22/tcp open ssh
8333/tcp open bitcoin
9998/tcp open distinct32
9999/tcp open abyss
Nmap done: 1 IP address (1 host up) scanned in 1.70 seconds

---

root@Bitcoin-1:~# cat ~/.litecoin/litecoin.conf

#----
rpcuser=ltcuser
rpcpassword=ltcpassword
rpcallowip=127.0.0.1
#----
listen=1
server=1
daemon=1
maxconnections=24
#--------------------
datadir=/root/LitecoinCore
#externalip=140.82.58.152

---

Basically TCP port 9333 isn't open... why ? (140.82.58.152 = host Bitcoin-1)

(+same problem exists with my other host 193.29.187.116 = host thc-1)

Another question: Should I install Electrum-LTC server, or Electrum-LTC users just connect to plain Litecoin Full Node at random ?

Okay, problem SOLVED !

It turns out that 'nmap' doesn't scan a port of 9333 by default. So I forced a full port scan.

root@Bitcoin-1:~# nmap localhost -p 1-65535

Starting Nmap 7.60 ( https://nmap.org ) at 2018-07-28 17:21 UTC
Nmap scan report for localhost (127.0.0.1)
Host is up (0.0000040s latency).
Other addresses for localhost (not scanned): ::1
Not shown: 65524 closed ports
PORT      STATE SERVICE
22/tcp    open  ssh
7075/tcp  open  unknown
8332/tcp  open  unknown
8333/tcp  open  bitcoin
8545/tcp  open  unknown
9332/tcp  open  unknown
9333/tcp  open  litecoin
9998/tcp  open  distinct32
9999/tcp  open  abyss
30303/tcp open  unknown
31416/tcp open  boinc

Nmap done: 1 IP address (1 host up) scanned in 5.88 seconds