I changed ISP and cant get my nodes running

[snorkel]

And for your own safety and privacy, delete the public IP from posts.
Add firewall rules for both protocols for all ports.

[HGPlays]

I have. they all have xxx in them

[HGPlays]

I added all the protocols for all ports - as you saw in the image above

[snorkel]

So lets do a receck…

1. Router - disabled malware protections, and DDOS prevention (in Firewalls rules).
2. Router - Added port forward rules.
3. Windows - added firewall rules.
4. Docker run command…
5. Clear browser cookies.

Post again the docker run commands from all nodes, between 3 backthicks ```
Anonimise WAN IP, wallet and email, replacing all caracters with xxx.
When you modify the docker command, stop storagenode, remove storagenode and then run.

[Alexey]

@snorkel

Maybe you can try using different ports for each node, even in the docker run command, like 28968:28968 tcp and udp.

it will not work on docker version without changing a binding port in the config file or with an option.
This command:

@snorkel

docker run -d --restart unless-stopped --stop-timeout 300 -p 28968:28968/tcp -p 28968:28968/udp

will make this node offline forever, because storagenode listening 0.0.0.0:28967/tcp 0.0.0.0:28967/udp inside the container

[Alexey]

Please check the firewall rule for 28967 UDP on your Windows machine, there also should be rules for 28968 UDP and 28968 TCP.
Then try to refresh a browser window or restart the service.

This error:

@HGPlays

2022-12-01T23:15:54.238+0100 FATAL Unrecoverable error {“Process”: “storagenode”, “error”: “server: listen tcp :28967: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.”, “errorVerbose”: “server: listen tcp :28967: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.\n\tstorj.io/storj/private/server.New:91\n\tstorj.io/storj/storagenode.New:379\n\tmain.cmdRun:210\n\tstorj.io/private/process.cleanup.func1.4:377\n\tstorj.io/private/process.cleanup.func1:395\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomConfigAndLogger:92\n\tmain.main:478\n\truntime.main:250”}

suggests that your docker node seems running with --network host, please check your virtual switch configuration (with Hyper-V Manager → Virtual switch Manager), your WSL2 (or Hyper-V VM for docker) should use a virtual switch connected to “Internal network”

[HGPlays]

So it looks about right on the virtual switch manager?

[Alexey]

Yes. And if you did not use --network host in your docker run command, there should be no conflict of occupied 28967

[HGPlays]

As seen in the image above i do have a rule in windows for the storj exe. So that whould be for the gui install.
now i also need one for the docker install?
It weird that it worked on the same machine before changing ISP

Well im gonna try to add another rule then.

[HGPlays]

So i just created 4 rules. two for 28967 with udp tcp and two for 28968 also
Going to attempt to launch the docker again

[Alexey]

@HGPlays

now i also need one for the docker install?

Usually yes. But you need also a second rule - for UDP.
Perhaps your firewall were disabled, but Windows enabled it back. So it’s better to configure it instead of disabling.

[HGPlays]

OKAY! so setting the port forward on both windows AND the router has fixed the docker install… So far so good!
Thanks.

now i need to just restart the GUI install and see if it is also ok.

[HGPlays]

Restarting the GUI also did the trick! awesome - thanks @Alexey