search

pi-node / instructions

266 stars 190 forks source link

Ubuntu Won't Allow P/W & Docker Desktop Not Working #97

Open Tzvi-R opened 3 years ago

Tzvi-R commented 3 years ago

I successfully downloaded, installed, & started the Pi NODE/Wallet, the Docker Desktop, and Ubuntu 20.04 LTS.

1) After successfully entering a USERID, Ubuntu wouldn't allow me to enter a PASSWORD - regardless of what I tried, nothing could be entered and accepted - the underscore cursor remained in place.

2) Getting back into the Pi Network program/App, while it displays that the Docker Program was successfully installed, it's also displaying that the Docker Daemon isn't running. Opening the Docker program/App gives me a container to run: docker run -d -p 80:80 docker/getting-started but there's nowhere within Docker to run this, and when I run it in Ubuntu, I receive an error message that "The command 'docker' could not be found in this WSL 1 distro".

How to resolve these issues, please???

Thanks much in advance!!!

Tzvi-R commented 3 years ago

PS.

When trying to solve this by getting into Docker, directly, it asks for a logon, which was never given.

OK - so I tried to set up a new one. However, setup required a Docker ID, which I don't have, and can't find anywhere...???

Tzvi-R commented 3 years ago

Hi again - so I changed the settings to use WSL distro 2, found that the Docker ID can be created, & even though Ubuntu still gave an error message, Docker became active - yay!

Now, with opening the Router Ports, nothing allows the "Pinging your computer" to pass. I've allowed the required ports for both inbound and outbound via Rules - no go. I've even shut down ALL firewalls - still no go. All 10 ports, 31400 - 31409 still display as NOT OPEN.

Ideas, please???

ihatejam commented 3 years ago

I'm confused by your mention of Ubuntu -- you don't actually need to install a WSL2 distro -- just activate WSL2 . All you need is the node/pi desktop app from node.minepi.com + Windows 10 (definitely bump it up to the latest build) and then install Docker Desktop with WSL2 enabled.

If your Docker daemon is not running - you need to fix that first -- this is not related to the Pi app. Might want to try the Docker forums -- however, I would consider uninstalling the lot and reinstalling it - it should just work out of the box. With Docker, just enable WSL2 (without actually adding any WSL2 distro).

Once you have Docker installed and the daemon is running, follow through the prompts on the Pi desktop app which should download a docker container called stellar-dummy -- All this container does is launch a port listener to help you configure and test your port-forwarding. Once the port forwarding is 100%, you need to leave your listener running until you are "recognized" as a potential node and the consensus container is dropped onto your setup.

Tzvi-R commented 3 years ago

Hi and thanks much for your reply.

I changed the settings to enable WSL2, and set up my account, so the next time around, Docker came up and remained active.

Not your "problem" but the App I'm using also needs access to 10 Ports. I opened/ allowed them all as both incoming and outgoing Ports within Windows Defender, but the App was still unable to "ping" my computer. I then completely shut down my Windows Defender (and all other) firewall(s), and still got the same result. Any ideas, please?

Thanks again and take care!

Tzvi

From: ihatejam @.> Sent: Thursday, April 1, 2021 3:58 PM To: pi-node/instructions @.> Cc: Tzvi-R @.>; State change @.> Subject: Re: [pi-node/instructions] Ubuntu Won't Allow P/W & Docker Desktop Not Working (#97)

I'm confused by your mention of Ubuntu -- you don't actually need to install a WSL2 distro -- just activate WSL2 . All you need is the node/pi desktop app from node.minepi.com + Windows 10 (definitely bump it up to the latest build) and then install Docker Desktop with WSL2 enabled.

If your Docker daemon is not running - you need to fix that first -- this is not related to the Pi app. Might want to try the Docker forums -- however, I would consider uninstalling the lot and reinstalling it - it should just work out of the box. With Docker, just enable WSL2 (without actually adding any WSL2 distro).

Once you have Docker installed and the daemon is running, follow through the prompts on the Pi desktop app which should download a docker container called stellar-dummy -- All this container does is launch a port listener to help you configure and test your port-forwarding. Once the port forwarding is 100%, you need to leave your listener running until you are "recognized" as a potential node and the consensus container is dropped onto your setup.

- You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpi-node%2Finstructions%2Fissues%2F97%23issuecomment-811888550&data=04%7C01%7C%7Cb65f1b784edd41859d9608d8f50db80e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637528786558665477%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=X7LPnqqh5YyME3QIDFVaYjJpXSJQUFwT6T8OeSuQ8ZA%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FATPWUAHP63ZS2Q3TFEP3HMLTGRUT5ANCNFSM42G3B3QA&data=04%7C01%7C%7Cb65f1b784edd41859d9608d8f50db80e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637528786558665477%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=XGjc6LMDSGyerfXnBdwOAc1gBkmOr4Tg0eoVQ%2F2cluU%3D&reserved=0.

ihatejam commented 3 years ago

could be two things -- either 1) your port forwarding was not done correctly or 2) your ISP cannot honor the port forwarding required to make this work.

First check this - go to https://www.ipfingerprints.com/portscan.php and check the port range 31400 to 31409 to see if they show as open. If they show as open then you have no issue. But from what you've said so far, I suspect that you actually do have an issue...

Start by doing this:- 1) Log into your router's admin portal (the router you configured the port forwarding on) -- check the WAN interface and note down the IP address it thinks it's been given by your ISP - write it down (do NOT share it here) - let's call it ipAddress1.

2) From your node PC, visit https://www.whatismyip.com/ and note down the IP address that it reports as your public IP address. let's call it ipAddress2

If ipAddress1 and ipAddress2 are NOT equal, then your ISP has not given you a "proper" public IP address. This is often the case when the subscriber base outnumbers the public IP addresses available to dish out. If you're in this boat, you can either move ISPs or get a VPN going like surfshark which I have personally used while travelling to keep my node going without having to worry about port forwarding.

On the other hand if ipAddress1 equals ipAddress2, then you've got to sanity check your config. To check if the listeners are fine on your local machine, make sure the stellar-dummy is running and check the following:-

3) see if your browser gives you a response to this URL:- http://localhost:31400

4) go to https://www.ipfingerprints.com/portscan.php and scan the port range 31400 to 31409 if they do not show your ports open AND 3) above does NOT error out, then I'd say you have a personal firewall or antivirus config issue that needs sorting out.

hope this helps.