This suddenly happened a few days ago. Ports 31400-31409 used to be all OPEN and now it’s NOT OPEN, except just 31409 which happens to be SoloHost. Before you ask, I have already created an inbound rule for my port on my firewall and assigned my IP for port forwarding. So how do I fix this? Is this a docker problem or pi network problem? By the way 31401-31403 and 31409 are all open on port checker and check open node ports on pi-mods. If anyone knows the solution, please reply to this thread with instructions, it would we very appreciated.
For me your post is missing a lot of context. What’s a Pi network? What’s SoloHost? What’s your OS? What’s your network setup? How does your compose file look like?
Good questions from @bluepuma77. I searched for Pi network and found something blockchain related which has something called “Pi node” that can be installed on Windows, Linux and macOS as well.
If I then search for “Pi node” using Google’s image search, I find similar screenshots. If I search for “Pi node pining” I find this: