Pinging my computer issue

[PetricaDascalu]

Hello, i tried to run the Pi Node, i opened the ports and then i pressed the check now button but the "pinging your computer" didnt checked in and it doesnt appear any errors.

[BeStephen1990]

are you running docker toolbox or docker desktop?

[BeStephen1990]

and have they been updated to latest versions?

Have you opened the proper ports in windows registry?

Have you forwarded the ports in your routers settings?

[BeStephen1990]

sometimes i have simply had to keep pressing "Check Now" until it works or does somethings....

[lgrosso-thinkswift]

im having the exact same issue, all ports are open and ICMP as well. Im able to ping the IP from outside no issues. Maybe its a bug?

[Aniket1900]

Hello, i tried to run the Pi Node, i opened the ports and then i pressed the check now button but the "pinging your computer" didnt checked in and it doesnt appear any errors.

I am having the same issue. Consensus container enabled: No, turning this "No" into "Yes" should solve this issue. I am still trying to find a solution once got will post it!!

[BeStephen1990]

from what i understand about this type of application is, the consensus container hasnt been released yet due to the mainnet not being fully operational/uploaded/online.... we are still in the testnet phase... the consensus container is kind of like the main log file that every node should have during mainnet in order to record and prove transaction records between the nodes and all other users...

[BeStephen1990]

i also do not have the consensus container but have been an operational node for a bit... 97.67% availability at the moment.,..

[BeStephen1990]

try throwing this into your url line and see what happens

http://testnet2.minepi.com:31401/

let me know

[lgrosso-thinkswift]

I get “OK FROM PORT 3401” as a result when pointing to my node.

Leo Grosso

On Jan 16, 2021, at 9:52 AM, BeStephen1990 notifications@github.com wrote:



try throwing this into your url line and see what happens

http://testnet2.minepi.com:31401/

let me know

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/pi-node/instructions/issues/41#issuecomment-761576031, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AF2VSEVXCZNV5ZZWG2QFDM3S2GR2TANCNFSM4U7RXE6Q.

[saadusufzai]

Having the same issue. is there a solution yet?

[hirenshah]

This is an issue with Pi Node because it still looks for Docker Toolbox components on Windows Home editions. Nothing much we can do until the application is updated.

[lcocea]

Had this symptom yesterday before I forwarded the ports correctly through my routers.

[8hallz8]

This thread has been helpful thanks everyone , Can anyone tell me if we need every port open or is my setup ok?

[lgrosso-thinkswift]

You should open up the two ports in red. Just add them to your firewall/port forwarding rules you’ve already setup.

Leo Grosso

On Mar 17, 2021, at 10:09 PM, 8hallz8 @.***> wrote:



This thread has been helpful thanks everyone , Can anyone tell me if we need every port open or is my setup ok? [image]https://user-images.githubusercontent.com/80854666/111562927-42a45280-8754-11eb-9d49-e80c7b6c7a94.png

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/pi-node/instructions/issues/41#issuecomment-801561855, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AF2VSESR3MSYHS6JKM2PBGTTEFOF5ANCNFSM4U7RXE6Q.

[nathusius]

Commenting to see if there is any solution, or any advice whether this is a known issue which cannot be fixed? I have same issue as OP, just a grey dot next to Pinging your Computer - it doesn't even try to check the ports after multiple attempts! Using Docker desktop, all up to date, 64 bit Win 10 Pro PC (10.0.19042), Technicolor router, using Windows firewall. Docker is installed and running stellar-dummy, ports are open and redirected OK on router, ping enabled on router, firewall rule added for all ports (inbound and outbound, just in case!). I can ping all the ports manually from outside my network and get a response OK FROM PORT 3140x; when I do that I can see a "REQ TO PORT: 3140x" in the Docker log for all ports, but there is no change in the log when I try the Ping Test from within Pi Network. I did see a mention somewhere to maybe open the ports in Windows Registry - are there any instructions for this, if it is necessary?! But my question is really whether I need to keep trying to fix this, as I am out of ideas, or can I leave it and assume all is actually working? I don't have any availability % showing yet, but only tried installing Docker this weekend. Any advice please?

[nicolae788]

Hi. No need to fw ports 31400-31409 in the win firewall. You need to check if docker service it's allowed and only this. Also use WSL2 and follow instructions from here https://github.com/pi-node/instructions/wiki/(EN)-New-instructions-for-docker-desktop-with-wsl2-(windows-2004). Wsl2 it's more reliable, for this use case, than Hyper-v. Do not forget to enable wsl2 in docker settings

If after setting up the environment as per instructions from the above link, stellar ports checker does not check all ports, but you are able to check externally the ports, then it's ok. It will take few days to get the consensus container

Good luck.

[nathusius]

Hi Nicholae, thanks for your reply and sorry for delay in reporting back! That was the instructions I followed, but I un-installed and tried it all again, getting exactly the same result - the port check from within Pi Node never even gets as far as pining the ports (see first screen grab above). I have even tried setting it all up on a different router and also called my ISP to check that they do allow the port forwarding, so I had almost given up getting this working, even though I have always seen that the ports are reported as open using https://www.ipfingerprints.com/portscan.php and they always have been, right from the beginning! But, I just had another check tonight, still no success with pinging the ports, but amazingly I just found this in the diag info:

Pi Node version number: 0.4.3 Operating system: WINDOWS 10.0.19042 (Microsoft Windows 10 Pro) Using Docker Toolbox: No Node installation date: 2021-04-01 Availability (up to 90 days): 41.24% from 2021-04-01 to 2021-04-15

My only conclusion is that it was working OK all along, but the port checking from within Pi Node is quite inconsistent between users, so not really a very good test! ;-) I will now leave it running for more hours and see if I get picked up as a test node! Thanks again

[Tasselhoff]

I'm having the same issue, and am getting "Unable to connect" for http://testnet2.minepi.com:31401

Is the testnet flaky?

[Tasselhoff]

That failed via my external 4G antenna using a Free SIM. I'm guessing they restrict upstream what can go through.

Did the same thing on my rural ADSL and it works fine. How long until it decides it can install the Consensus Container?

[nathusius]

Testing via the built-in port checker never worked at all for me, so I just left it running anyway and eventually got picked up, but it probably took a couple of weeks - you do need to be patient. I am usind a wired to VDSL router, I did have to setup a rule to allow incoming connections on the pi ports and configure my network adapter for a fixed IP address (so that the router rule remained valid after a PC reboot!). All you can really do is check your ports are open at https://www.ipfingerprints.com/portscan.php then just leave it runnig and wait!

[ihatejam]

@Tasselhoff The chances of getting a "proper" public IP address that allows port forwarding on a standard 4G mobile connection is zero to none. The consensus container will not be able to function if those ports are not open on the router and forwarded to your node PC. Your best bet if, 4G is your only option, is to try using a VPN service that works around your ISP's restrictions like Surfshark - which is what I used to keep my node going on my laptop when I flew down to South Africa for a while during the Covid lockdown recently. Surfshark will also get your port forwarding going on an ADSL line that has similar restrictions. I was forced to use both 4G and ADSL while travelling through South Africa. Somewhere in one of this github links there is another user who successfully got the port-forwarding working with Surfshark after I recommended it.

[ihatejam]

@nathusius FYI -- node version 0.4.4 is now available for download on the node.minepi.com site

[nathusius]

@ihatejam Thanks; yes, been there, done that after your earlier heads-up - all working again with more incoming connections now!

[Tasselhoff]

@Tasselhoff The chances of getting a "proper" public IP address that allows port forwarding on a standard 4G mobile connection is zero to none. The consensus container will not be able to function if those ports are not open on the router and forwarded to your node PC. Your best bet if, 4G is your only option, is to try using a VPN service that works around your ISP's restrictions like Surfshark - which is what I used to keep my node going on my laptop when I flew down to South Africa for a while during the Covid lockdown recently. Surfshark will also get your port forwarding going on an ADSL line that has similar restrictions. I was forced to use both 4G and ADSL while travelling through South Africa. Somewhere in one of this github links there is another user who successfully got the port-forwarding working with Surfshark after I recommended it.

My 4G router did allow port forwarding, so I'm assuming it was the provider disabling it upstream. As soon as I did the same thing for ADSL it worked fine. But if I do need to use the 4G (which has 30x better upload speed than my ADSL) I'll definitely consider a VPN, thanks.

[ihatejam]

@Tasselhoff No worries - glad your ADSL connection worked out ---

Just a side note to explain a bit more about why 4G doesn't "cut the cheese" ...

It's considered wasteful for mobile providers to hand out real public IP addresses to (4G) mobile devices, especially since a provider's public IP range allocation is finite and there are way too many mobile devices for it to serve. 99.9% of mobile devices are fine with NAT'd addresses, so that's what they dish out -- and that's what messes up port forwarding. Many cable-based ISP's actually operate on the same principle - using NAT to extend their userbase reach/capability beyond their limited (allocated) IP range. People who end up with these ISPs will fail the port test, and would have to use VPN.

[smith111707]

I'm experiencing the same issue. Any solution or workaround so far, please? The issue was reported 10 (ten!) months ago!

[Rammyak]

Have tried all around my router but I couldn't get port forwarding option. All I could see is port mapping and UPnP. Will it work if I just leave my UPnP enabled or what else can I do. Thanks

[ihatejam]

@Rammyak you may want to create your own issue thread if you want help - And mention the brand and model of router you are using.

[ASGBOB]

I have founded a fix for this issue just turn off your real time windows protection

[Tasselhoff]

I have founded a fix for this issue just turn off your real time windows protection

A. That won't fix an upstream issue.

B. I hope it's a joke.

[ASGBOB]

just try it

[Tasselhoff]

just try it

I used a network sniffer. The problem was not on the windows machine. And suggesting people remove realtime protection is irresponsible as well as being an incorrect solution.

[ihatejam]

@ASGBOB There is no need to turn off any windows threat protection feature - and there's no way to justify requiring anyone to do so just to get a piece of software working. Perhaps as a troubleshooting step, but not for actually running the software on a permanent basis. Offering this as a solution is reckless! At the most, people may need to add a few firewall rules into Windows Firewall as in the user-contributed wiki notes - https://github.com/pi-node/instructions/wiki

[GoldCash-Pool]

I had the same problem that he didn't ping my computer. The solution to the problem was that it was not activated in windows hyper v for me

but now he not will start the node

[cheme75]

Same no ping on win 10 pc- got docker running with no issues, shows server listening on ports 31400-31409, stellar-dummy is running. On Pi node info, shows all ports green so open - I click "check now" and I get downloading ports listener with green check, starting ports listener with green check, then pinging your computer does nothing. I initially got the node running on an old laptop but it was old and too slow. Left docker and node running in background but too difficult to work on the machine. So, I moved HD with win10 to a less old desktop, got win10 re-authorized, updated all drivers - reinstalled docker with wsl2, now the docker and node seem to be running reliably. I'm not sure how to get the official container and not sure if the ping is a problem hindering my node to be accepted. ipfingerprint port scan shows external ip and shows all ports are open, none are filtered. Kind of frustrating to be sort of stuck in limbo. Any help is appreciated!

[okotu]

I need help Pinging your computer is not checked on my node and this is really making me restless, what do I do ?

[electrok-d]

I have the same problem. All ports are verified as open from the outside and the Pi Node app is communicating with Docker. It is stuck at "Pinging your computer".

From what I've read, which might not be true, it is a known issue and that the Pi team is focusing on the MainNet launch rather than addressing it.

[cheme75]

I have the same problem. All ports are verified as open from the outside and the Pi Node app is communicating with Docker. It is stuck at "Pinging your computer".

From what I've read, which might not be true, it is a known issue and that the Pi team is focusing on the MainNet launch rather than addressing it.

Another issue thread had some recent replies to my posts - see: https://github.com/pi-node/instructions/issues/75#issuecomment-1009197507

I also got the impression it is a glitch in the pi app since it seems many have same issue. But looking at docker, I see a tiny bit of I/O. Not much yet, but signs of some minimal activity. I think it’s a matter of finding some reliable communication with a prospective node before it gets a consensus container. With close to 30million users, there could be quite a large number setting up nodes. I know my prior pc was not consistently available, so I should have moved the hard drive much earlier. Now I’m kind of late to the party.

3/26 Update: it just took some time - all is working and consensus container loaded eventually and is functioning