Open mackyzap03 opened 3 years ago
Have you done the port test in the Pi app? Doing so should push the "stellar-dummy" container to your pc and then start it up.
Firewall issue. Ports working? (Use all tests that have been posted everywhere). Have you added Docker and its programs as Allowed Apps on Firewall?
yes i do port test on the app but still not working. im stuck at the last phase
On Mon, 10 May 2021 at 18:09, ihatejam @.***> wrote:
Have you done the port test in the Pi app? Doing so should push the "stellar-dummy" container to your pc and then start it up.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/pi-node/instructions/issues/122#issuecomment-836506624, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUAQIXPTJVCJE4NZPELPPADTM6WD5ANCNFSM44QYTQKQ .
Are you saying that going into the Windows Cmd window, and doing the "netstat -aon" command the ports 31400-31409 have a status of "LISTENING"?
@mackyzap03
In docker desktop, do you see a container called "stellar-dummy"?
If you don't have it, (or if you have it, but it is not in a running state) then a netstat or port check will not yield any results. The action of starting the portchecker inside the node app, has these distinct stages as far as i can tell. 1) Checks if Docker is "ready". 2) Checks to see if the "stellar-dummy" container exists and if not, pushes it down to Docker. 3) Starts the "stellar-dummy" container which then listens on ports 31400-31409 while it is in the running state.
After point number 3), and after the stellar-dummy is shown as running, then, as pilgrim103 mentioned, you can execute "netstat -ano" in a cmd or powershell window. It should show you that those ports are being "listened on".
This does not mean that the ports have been forwarded from your public/external ip address to the nodes private/internal ip address.
Before moving further, please confirm if the stellar-dummy container is present and in the running state.
Also, please forward a screenshot of your troubleshooting page in the Node app.
docker says " no container running. what should i do pls help