Consensus container absent after updating Windows and Docker.

[hawjiang5349]

node reachable from outside of your home network -- Are the ports forwarded properly? Yes What does https://www.ipfingerprints.com/portscan.php report for the ports that are meant to be forwarded? (Please do not post pictures containing your public/external IP addresses) all open Do you leave your Node running all the time? 24/7

Any Idea?

[ihatejam]

Somehow, the consensus container did not download for you when you were enabled for consensus on the network. Please check if this works for you (I know you have already done some of this before - but try it in this order.. . Inside the app, on the node switch page, please try turning off the node. Go to Docker and activate the "Stellar Dummy" Container. Go back to the Node app and go to the "Visit tech setup" displayed under the switch. Expand the "Open router ports section" and then click on the "Check now" button - at the end of the successful port check, continue on and see if the consensus container is sent to your system. If it is not sent down, there may be something outside of your network blocking this from happening.

[hawjiang5349]

Somehow, the consensus container did not download for you when you were enabled for consensus on the network. Please check if this works for you (I know you have already done some of this before - but try it in this order.. . Inside the app, on the node switch page, please try turning off the node. Go to Docker and activate the "Stellar Dummy" Container. Go back to the Node app and go to the "Visit tech setup" displayed under the switch. Expand the "Open router ports section" and then click on the "Check now" button - at the end of the successful port check, continue on and see if the consensus container is sent to your system. If it is not sent down, there may be something outside of your network blocking this from happening.

I follow your step and do again, switch off node, run check now, stellar dummy start automatically in docker, 31400-31409 all port open, switch on node. Nothing I do, I just leave it.

[hawjiang5349]

I feel like Pi network team doesn't release their consensus container to let people download.

[SumpBeast19]

I feel like Pi network team doesn't release their consensus container to let people download.

I have the same issue as you here, pi container absent and ports checker exited. I feel let out too !

[SumpBeast19]

I have the same issue here. container doesn't seem to deploy in my docker. got the stellar dummy but that's it

[NeyMR]

I have the same issue here. container doesn't seem to deploy in my docker. got the stellar dummy but that's it

the only thing that should be running in the container is the Pi-consensus/pinetwork/pi-node-docker the port tester/stellar-dummy should remain exited while node is on the blockchain, for port forwarding please provide your router model and will try to help resolve the closed ports issue.

thanks for your understanding, we're all in this together 😁👍

[SumpBeast19]

Thing is the only container deployed in my docker is the stellar dummy ,i have no issue with port forwarding

On Mon, Aug 1, 2022 at 10:45 AM NeyMR @.***> wrote:

I have the same issue here. container doesn't seem to deploy in my docker. got the stellar dummy but that's it

the only thing that should be running in the container is the Pi-consensus/pinetwork/pi-node-docker the port tester/stellar-dummy should remain exited while node is on the blockchain, for port forwarding please provide your router model and will try to help resolve the closed ports issue.

thanks for your understanding, we're all in this together 😁👍

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

[NeyMR]

Thing is the only container deployed in my docker is the stellar dummy ,i have no issue with port forwarding

On Mon, Aug 1, 2022 at 10:45 AM NeyMR @.***> wrote:

I have the same issue here. container doesn't seem to deploy in my docker. got the stellar dummy but that's it

the only thing that should be running in the container is the Pi-consensus/pinetwork/pi-node-docker the port tester/stellar-dummy should remain exited while node is on the blockchain, for port forwarding please provide your router model and will try to help resolve the closed ports issue.

thanks for your understanding, we're all in this together 😁👍

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

what version of Docker are you currently running? if need of update please update and do a clean install of docker https://docs.docker.com/desktop/release-notes/

you can download and see your current running version compared to latest version, let us know the results😁👍

[SumpBeast19]

I have uninstalled and reinstalled the latest version as of today as a means to try to solve my issue already 😅

On Mon, Aug 1, 2022 at 8:47 PM NeyMR @.***> wrote:

Thing is the only container deployed in my docker is the stellar dummy ,i have no issue with port forwarding

On Mon, Aug 1, 2022 at 10:45 AM NeyMR @.***> wrote:

I have the same issue here. container doesn't seem to deploy in my docker. got the stellar dummy but that's it

the only thing that should be running in the container is the Pi-consensus/pinetwork/pi-node-docker the port tester/stellar-dummy should remain exited while node is on the blockchain, for port forwarding please provide your router model and will try to help resolve the closed ports issue.

thanks for your understanding, we're all in this together 😁👍

— Reply to this email directly, view it on GitHub

173 (comment)

https://github.com/pi-node/instructions/issues/173#issuecomment-1201300364 , or unsubscribe

https://github.com/notifications/unsubscribe-auth/A2KB3DNA3NKMFTFYDZ25AZLVW7PHFANCNFSM5CD7L7UQ . You are receiving this because you commented.Message ID: @.***>

what version of Docker are you currently running? if need of update please update and do a clean install of docker https://docs.docker.com/desktop/release-notes/

you can download and see your current running version compared to latest version, let us know the results😁👍

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

[SumpBeast19]

I have finally been able to pick up the container, I have disabled wsl2, restarted computer, and then went back to docker to check the WSL2 engine, restarted docker and everything worked fine. The pi-consensus container is now up and running ! i really can't tell what was the problem at first. Thanks alot for trying and reaching out to me !

On Mon, 1 Aug 2022 at 23:55, Pier-Luc Rioux @.***> wrote:

I have uninstalled and reinstalled the latest version as of today as a means to try to solve my issue already 😅

On Mon, Aug 1, 2022 at 8:47 PM NeyMR @.***> wrote:

Thing is the only container deployed in my docker is the stellar dummy ,i have no issue with port forwarding

On Mon, Aug 1, 2022 at 10:45 AM NeyMR @.***> wrote:

I have the same issue here. container doesn't seem to deploy in my docker. got the stellar dummy but that's it

the only thing that should be running in the container is the Pi-consensus/pinetwork/pi-node-docker the port tester/stellar-dummy should remain exited while node is on the blockchain, for port forwarding please provide your router model and will try to help resolve the closed ports issue.

thanks for your understanding, we're all in this together 😁👍

— Reply to this email directly, view it on GitHub

173 (comment)

https://github.com/pi-node/instructions/issues/173#issuecomment-1201300364 , or unsubscribe

https://github.com/notifications/unsubscribe-auth/A2KB3DNA3NKMFTFYDZ25AZLVW7PHFANCNFSM5CD7L7UQ . You are receiving this because you commented.Message ID: @.***>

what version of Docker are you currently running? if need of update please update and do a clean install of docker https://docs.docker.com/desktop/release-notes/

you can download and see your current running version compared to latest version, let us know the results😁👍

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

[NeyMR]

I have finally been able to pick up the container, I have disabled wsl2, restarted computer, and then went back to docker to check the WSL2 engine, restarted docker and everything worked fine. The pi-consensus container is now up and running ! i really can't tell what was the problem at first. Thanks alot for trying and reaching out to me !

On Mon, 1 Aug 2022 at 23:55, Pier-Luc Rioux @.***> wrote:

I have uninstalled and reinstalled the latest version as of today as a means to try to solve my issue already 😅

On Mon, Aug 1, 2022 at 8:47 PM NeyMR @.***> wrote:

Thing is the only container deployed in my docker is the stellar dummy ,i have no issue with port forwarding

On Mon, Aug 1, 2022 at 10:45 AM NeyMR @.***> wrote:

I have the same issue here. container doesn't seem to deploy in my docker. got the stellar dummy but that's it

the only thing that should be running in the container is the Pi-consensus/pinetwork/pi-node-docker the port tester/stellar-dummy should remain exited while node is on the blockchain, for port forwarding please provide your router model and will try to help resolve the closed ports issue.

thanks for your understanding, we're all in this together 😁👍

— Reply to this email directly, view it on GitHub

173 (comment)

https://github.com/pi-node/instructions/issues/173#issuecomment-1201300364 , or unsubscribe

https://github.com/notifications/unsubscribe-auth/A2KB3DNA3NKMFTFYDZ25AZLVW7PHFANCNFSM5CD7L7UQ . You are receiving this because you commented.Message ID: @.***>

what version of Docker are you currently running? if need of update please update and do a clean install of docker https://docs.docker.com/desktop/release-notes/

you can download and see your current running version compared to latest version, let us know the results😁👍

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

Glad you got it all sorted out, always keep docker updated when possible and any further assistance please don't hesitate to ask, we're all in this together 👍👍