Mac OS Please

[yohannchin]

Hi, it seems there’s no tuto for mac os and even though docker is working fine to run the blockchain, I’d like to open those ports but its not the same as windows, and seems more complicated, coulf anyone help please.

[lanctot6]

It seams I am having similar problems as @yohannchin . I am using a Mac/os and also am getting "not open" on my port status.

[RyanG2016]

I have all of my ports open and forwarded but each time I run the port checker within the node, it tells me it failed and random ports show as not open. It's different everytime. I've run the fingerprinting test and confirmed all ports open. Has anyone gotten this working on macOS 10.15.7? Docker is showing the port requests on each port.

[ihatejam]

@RyanG2016 sounds like you're good to go if ipfingerprints says that the ports are open while the stellar-dummy container is running. Just move the switch to the On position and wait to be selected as a node candidate (could take a while). Once that happens, the consensus container will be sent down to your setup after which the stellar-dummy will auto-stop and the consensus container will start up

[RyanG2016]

I thought since it wasn't doing anything something wasn't right. I'll leave it running.

[censomin]

I've turned off the firewall and set port forward in my router, but still get failure of port check. My MacOs is 10.15.7.

[nathusius]

Several recent threads on here with the same question! The built-in port checker results are inconsistent, so probably best to just ignore - I never even got the port checker to run at all, yet I am running the node just fine! Better to check your ports with ipfingerprints, if that says your ports are all open (with the "stellar-dummy" container running in Docker) then you are all good, just make sure the node switch is on then leave it all running continuously (ideally 24/7) and wait to get picked up as a node candidate. I wasted a LOT of time trying to get the port checker to run, but was actually just chasing a non-exisitent problem!!

[nathusius]

Have a read of this thread: https://github.com/pi-node/instructions/issues/103

[nathusius]

Pasted from above thread:

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

[xtrycatchx]

if you're at home and assuming you have access to your router's admin portal, then just enable port forwarding of the port range 31400 to 31409 to the IP Address of the machine where you're running the PI Node

hope this helps

[pjockey]

In 2022, still having troubles with this exact same thing.

if you're at home and assuming you have access to your router's admin portal, then just enable port forwarding of the port range 31400 to 31409 to the IP Address of the machine where you're running the PI Node

this is exactly what I've done.