Ports not opening

[madiebrummie]

I have followed all the tutorials and have set rules on pc and router but still cant seem to open ports. Pi app says Ok "downloading ports listener" OK "starting ports listener - UNABLE "pining your computer". I think the issue may be with the router - I have EE smart hub and I am unable to follow last instruction which is to enable WAN ping. It says;

_"an walkaround is to enable Virtual Server and point it to your computer IP address. Under protocol type you should be able to manually write the protocol number which for ICMP is 1."

But I am unsure how to do this. Can someone help please.

[msayed]

i have the same issue i have even allowed all ports and disabled the firewall and same issue

[ihatejam]

I thought I'd take the opportunity to google port forwarding on your ee hub for you - and I was extremely surprised (NOT) that the info is publicly available 🤪 here... https://ee.co.uk/help/help-new/broadband-and-landline/routers-help/set-up-portforwarding

If you've done the above for the relevant ports (31400 to 31409) and the node desktop app still reports the ports as closed then do the following:- While the "stellar-dummy" is running -- check if the ports are open using https://www.ipfingerprints.com/portscan.php

If it also reports that your ports are closed then write down the public IP address ipfingerprints thinks you're on [Note: do NOT post your public IP address here]. Compare the public IP address reported by ipfingerprints with the public IP address reported by the WAN interface on your router (you'll need to log into your router config -- and it is NOT the address starting with 192. ). If the two IP addresses do not match, then it is likely that your ISP does not hand out "real" public IP addresses. This is common practice in places where the demand for IP addresses is larger than the IP address block allocated to your ISP. To resolve this, you can do the following: a) ask your ISP if they can give you an IP address that allows port forwarding. b) switch to an ISP that allows/facilitates port forwarding. c) use a VPN provider that automatically takes care of port forwarding like Surfshark

[madiebrummie]

@ihatejam It is now saying some are open and some are not

But using the ipfingerprints it says all are open. would you suggest going down the VPN route.

Kind regards

[madiebrummie]

Also this is what I have on trouble shoot.

[ihatejam]

If ipfingerprints says they're open, then you should be good to go. Leave it running as is for a few days - Once the system recognizes you as a viable node candidate, it will send a consensus container to your pc which will then start "talking" to other nodes on the testnet. It could take a while before you're selected to run the consensus container.

[riodda]

Hi, i have the same problem of @madiebrummie , ports are open and show open with ipfingerprints

[ihatejam]

@riodda If your ports are showing as open with ipfingerprints, then you don't have a problem

[riodda]

It's a bit confusing, there is no consensus container running as the port checker container check fails....

[ihatejam]

@riodda You're fine in that state if ipfingerprints shows the ports are open. Right now you've not been chosen to run the consensus container yet. Give it a few days running in its current state so that they can figure out your machine's availability as a node candidate. Once you're selected to be a node, the consensus container will be pushed down to you. When that happens, the Portchecker (stellar-dummy) container will automatically unload before the consensus container is started up.

[foscoj]

This issue should be renamed to "ping test fails, even though the ports are open, checked by ipfingerprints" ;)

Same situation here, ports are open, but Pi Node ping test states they are not.

[NeyMR]

This issue should be renamed to "ping test fails, even though the ports are open, checked by ipfingerprints" ;)

Same situation here, ports are open, but Pi Node ping test states they are not.

if you need help https://t.me/PiNodechat bulding a small serious operator community to help each other, your more than welcome to join 😁👍

[azou2022]

I have the some mitake The port doesn't open Can somebody guide me to resolve this problem

Le mer. 21 sept. 2022 à 11:25, foscoj @.***> a écrit :

This issue should be renamed to "ping test fails, even though the ports are open, checked by ipfingerprints" ;)

Same situation here, ports are open, but Pi Node ping test states they are not.

— Reply to this email directly, view it on GitHub https://github.com/pi-node/instructions/issues/103#issuecomment-1253506960, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2QAXKHRPPWU3YKHJ4XSOH3V7LPBNANCNFSM42URVYBQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[manpou111]

I thought I'd take the opportunity to google port forwarding on your ee hub for you - and I was extremely surprised (NOT) that the info is publicly available 🤪 here... https://ee.co.uk/help/help-new/broadband-and-landline/routers-help/set-up-portforwarding

If you've done the above for the relevant ports (31400 to 31409) and the node desktop app still reports the ports as closed then do the following:- While the "stellar-dummy" is running -- check if the ports are open using https://www.ipfingerprints.com/portscan.php

If it also reports that your ports are closed then write down the public IP address ipfingerprints thinks you're on [Note: do NOT post your public IP address here]. Compare the public IP address reported by ipfingerprints with the public IP address reported by the WAN interface on your router (you'll need to log into your router config -- and it is NOT the address starting with 192. ). If the two IP addresses do not match, then it is likely that your ISP does not hand out "real" public IP addresses. This is common practice in places where the demand for IP addresses is larger than the IP address block allocated to your ISP. To resolve this, you can do the following: a) ask your ISP if they can give you an IP address that allows port forwarding. b) switch to an ISP that allows/facilitates port forwarding. c) use a VPN provider that automatically takes care of port forwarding like Surfshark

are you sure? im faciing isp block issue on pi ports i have nord and windscribe both didnot work will surfshark work? is there way to configure it? should i buy it? how sure are you? were your ports reported open when you were connected to surfshark vpn? which server you were using mention configurations and proof that it worked nord and windscribe didnot so i have suspicion weather it will work...according to their website port fordwarding isnot supported

[mgrove99]

I found that in docker, stellar-dummy was NOT running. In the top search bar of docker, type in stellar (make sure u spell it right) and you will find the container. Press the START button for the container then try the port checker again.