Hi,
don’t know what I’m missing here. Installed GUI version 0.13.2.1 on macOS Sierra, it synchronized successfully but never reported a single inbound connection. The port 9333 is open. I also have a Bitcoin Core running on the same machine and it has both inbound and outbound connections.
you will only get outbound connections to relay your transactions unless you have a .conf file saved in your appdata folder that looks like this:
server=1
daemon=1
rpcuser=(your address you are solo mining to)
rpcpassword=x
rpcallowip=127.0.0.1
rpcport=9333
port=9332
gen=1
gen=1 is the key to get incoming connections because you are generating blocks with this setting so miners will connect to your server to get the hash work to solve a block…you’ll notice faster confirmations if you do this as I know I did…rather than just hoping my 8 outgoing were going to pool servers rather than just opened wallets…
I am willing to bet if you start litecoin-qt.exe using command prompt by cd to where you have it saved and then orun it by typing litecoin-qt.exe -server -gen=1
or by just opening console under help debug window and then type help there and find the command that generates blocks which use to be:
setgenerate true
…hope this helps
After several attempts, including compiling the 0.14.99 litecoind it finally worked for me with the litecoin.conf in the data directory.
btccore won’t list any incoming connections until it’s synched. But the network config plays a large part in that. The log file will probably show if there are attempts to connect as incoming that are failing for some reason, but I’ve found the solution can be as simple as using my 5G phone instead of whatever you’re using for a wan interface. btccore usually takes somewhat longer (< an hour) after startup, to show incoming connections, and you have to have the “allow incoming network connections” flag on. Having trouble with this with LTC but I expect because LTC syncs so much faster than BTC so it hasn’t been on the internet for as long as btccore which takes a week? Pretty close…to sync on wifi. So maybe next week this ltccoind will allow incoming connections. Check port 9333 for incoming connections.
also I think the first reply is confused about a few things.
first the difference between inbound and outbound connections is mainly who initiated the connection, a remote computer or your computer. Outbound connections are connections that your computer initiated, such as at startup so it can re-sync the full node copy of the relevant blockchain. So you’re going to get those right away. There are relatively few impediments to outbound connections, so they are easy and reliable to start. You’ll see those in the Peer tab in the Gui or with getpeerinfo in the GUI console.
The inbound connections are a different story. I’m not exactly sure what is required for them, but from what I’ve read for both btc and ltc you need an inbound listening port (default 8333 for btc and 9333 for ltc). You have to negotiate any routers which might block incoming traffic to your server. With btc this was easy, the problem was solved just using my 5g phone to make the connection instead of wifi through NAT. If that’s your block then you need some kind of port-forwarding to send connections coming into your NAT server at that port to your backside IP address at that port. A VPN connection might solve the problem. Maybe. If you’re using the right type of VPN, UDP or TCP.Might be a good argument for using OpenVPN based VPN instead of Wireguard. I’m not sure, full node for ltc synchs so quickly relative to btc that my problem might just be that it has not been online long enough to be discovered.
Might be that my phone ISP has blocked that port since I last ran bttcore.
I don’t know. I do know that for btc there are websites out there which you can use to scan port 8333 from the Internet at large (should be possible to do that just with 127.0.0.1:8333 (http) just to see if you get a response even from the same server, because if not then you’re not getting anything from the Internet).
what about the litecoin.conf options above?
daemon, server maybe. Those are startup options for litecoind and they can be used in the GUI console.
What about litecoin-cli? Then you have to have upnp running, right?
./litecoin-cli
Litecoin Core RPC client version v0.21.3
…not exactly…
./litecoin-cli -getinfo
{
“version”: 210300,
“blocks”: 2784090,
“headers”: 2784090,
“verificationprogress”: 0.9999997210964335,
“timeoffset”: 0,
“connections”: {
“in”: 0,
“out”: 10,
“total”: 10
},
“proxy”: “”,
“difficulty”: 42706149.83201914,
“chain”: “main”,
“keypoolsize”: 1000,
“unlocked_until”: 0,
“paytxfee”: 0.00000000,
“balance”: 0.00000000,
“relayfee”: 0.00001000,
“warnings”: “”
}
I’ll have to play with the cli a bit. No pun intended.
Hm. At least RPC?
Hopefully I do not then need UPnP. This is where the question of what exactly those incoming connections are doing becomes important. Are they other full-nodes? Likely to connect as outgoing, it’s easy to hit 10, I’m not sure what sets that limit. Light wallets? Why would they connect to your full-node? But something will, eventually. Why exactly? I’m not sure. Miners? Same question. Pool servers? Probably more likely that you connect to them than they to you. If you’re going to try to mine on/with your full-node, that’s another issue. Seriously would suggest pool mining, solo-mining a popular coin is “a challenge”. Very-low odds of ever getting a block to mine.
All exciting stuff, but this was FAR easier to solve with the btccore client. Intriguing question. Will follow up later if I figure it out.
But apparently just to run as a full-node, it doesn’t need incoming connections. That would mean either a full-node, a miner or at least a wallet working off your full-node.
I think.
Maybe a hacker. Could be.