search

pi-node / instructions

266 stars 190 forks source link

i cant open the ports #44

Open yaronbabi opened 3 years ago

yaronbabi commented 3 years ago

I did exactly everything necessary according to the guide and the ports do not open for me, can anyone help me?

BeStephen1990 commented 3 years ago

you could help us out by giving us some information on your current setup, what programs you have installed and their versions...

we may be able to narrow things down for you then....

yaronbabi commented 3 years ago

i got win 10 pro, i opened up a new rule like the instructions i opened the port's in my router, i don't have any antivirus software,doker desktop running good.

ihatejam commented 3 years ago

Hi,

Assuming you know your way around your router -- Log into its admin portal and check to see what public IPv4 address you've been assigned by your ISP on the WAN link. Write it down. Next -- from your browser go to https://www.whatismyip.com/ and check what that site says your public IPv4 address is.

A. If the site matches the IPv4 address you wrote down, then the problem is likely to be local on your setup - although it looks fine to me. It is also possible that your ISP may not be allowing port forwarding (although unlikely). You can sanity check your setup by using https://www.ipfingerprints.com/portscan.php

B. On the other hand, if the IP address on the website does not match the IP address you've written down, then the problem is with your ISP -- in that, they are not issuing you with a true public IPv4 address -- so there is no way to forward the required traffic to your PC (so that the forward rules can send it on to the Node app). This is common practice in locations that do not have enough public IP addresses allocated for use by the public. If this is your issue, then talk to your ISP to see if it can be arranged or switch to an ISP that can give you a real public IP address. If that goes nowhere, then use a VPN that supports port forwarding (usually not free)

ihatejam commented 3 years ago

Just wanted to say - in case you were thinking of doing it -- please do NOT post your public IP address here!

yaronbabi commented 3 years ago

I did everything as written in the instructions I even bought a VPN The ports are open according to CMD Everything is set correctly in a firewall and still the ports are not open in the IP NODE test I'm really desperate !!!!

yaronbabi commented 3 years ago

Hi,

Assuming you know your way around your router -- Log into its admin portal and check to see what public IPv4 address you've been assigned by your ISP on the WAN link. Write it down. Next -- from your browser go to https://www.whatismyip.com/ and check what that site says your public IPv4 address is.

A. If the site matches the IPv4 address you wrote down, then the problem is likely to be local on your setup - although it looks fine to me. It is also possible that your ISP may not be allowing port forwarding (although unlikely). You can sanity check your setup by using https://www.ipfingerprints.com/portscan.php

B. On the other hand, if the IP address on the website does not match the IP address you've written down, then the problem is with your ISP -- in that, they are not issuing you with a true public IPv4 address -- so there is no way to forward the required traffic to your PC (so that the forward rules can send it on to the Node app). This is common practice in locations that do not have enough public IP addresses allocated for use by the public. If this is your issue, then talk to your ISP to see if it can be arranged or switch to an ISP that can give you a real public IP address. If that goes nowhere, then use a VPN that supports port forwarding (usually not free)

can you recimmend on a good vpn can do this?

ihatejam commented 3 years ago

I've personally tested this with SurfShark and it worked fine for me. However many favor NordVPN (and they speak very highly of it). Neither the Pi project nor myself are affiliated with any VPN service. Essentially any VPN service offering port-forwarding will suffice -- I would check and test what works best for you in your environment as well as what support they offer.

yaronbabi commented 3 years ago

I've personally tested this with SurfShark and it worked fine for me. However many favor NordVPN (and they speak very highly of it). Neither the Pi project nor myself are affiliated with any VPN service. Essentially any VPN service offering port-forwarding will suffice -- I would check and test what works best for you in your environment as well as what support they offer.

Thank you so much my friend it worked like a charm with Surfshark.

ihatejam commented 3 years ago

You're welcome!

Now leave the port listener running with the ports open. It does not do much, but leaving it all running helps you get identified and selected for running a node. Once that happens, a consensus docker container will be deployed to your device. Bear in mind that this is still in testing phase - so it could take a while. In the node app, on the screen with the switch to "turn the node on", you can keep tab of your setup by clicking on the Troubleshooting near the bottom right of that screen with the switch on it. On that Troubleshooting screen, the most important part right now for you is to keep an eye on your Availability percentage - it will not be very meaningful right now since you've only just started out, but try to keep it over 90% to improve your chances of being selected for a node (I guess closer to 100% could make you a Supernode candidate). Once you are running the node/consensus container (this will only arrive later after you're selected based on your availability %) it will eventually show you "Consensus container: running".

Good luck!

yaronbabi commented 3 years ago

thanks you i do that 👍

m-henderson commented 3 years ago

@yaronbabi I had the same issue. close docker, close pi. Open ports then run docker and run pi. the ports wont open if they are trying to be used by a service.