Node is about a week old, before the reboot it was working just fine. Its running in docker on a ubuntu server VM hosted by proxmox. I think its an internal network issue, Ive double checked all my port settings but the port forwarding doesn’t seem to be open when tested by a checker. I tried forwarding ports 7777 to the node as thats the error given in the dashboard but no change, I noticed port 7777 isnt in the docker run command I used to configure originally but not sure if thats an issue or not. I have a few other machines with port forwarding rules on the router working.
Did you try the Port Forward tester both with your DDNS hostname, and IP? Your port-forwarding/firewall may be fine… but if dynamic DNS isn’t updating then the port checker may be trying the wrong/old IP.
Your logs show the satellites are trying to connect to you at 66.10.74.100:28967 - that’s what your ddns should resolve to? (Just checking as you seem to be debugging from 198.44.129.101)
yes, 66.10.74.100:28967 is my current WAN IP where the storjnode lives, the other IP is from Mullvad VPN service on my laptop. Thanks for putting out suggestions.
proxmox showing VM has 192.168.1.214 and router also showing 192.168.1.214 as a static assigned IP to storjnode. And I can SSH into it at 192.168.1.214.
Do you have another Linux system you can test from on your 192.168.x.y network? It would be good to test if the port is open internally properly. Something like this:
nc -v 192.168.1.214 28967
…should show it connect and block forever if the port is open. If not, it should show connection-refused. (You can test by using a wrong port: like “nc -v 192.168.1.214 28968”).
If the port is open internally… then something is wrong with the port-forwarding on your router.
We onto something now, whats weird is the nodes showing the ports open in an above screen shot. The issue started after I rebooted my proxmox host/vm due to a new kernel update. So maybe its proxmox, but Ive got the proxmox vm firewall disabled.
I see a screenshot above saying the firewall is open for 28967. But that doesn’t mean the Storj process is running and listening on 28967. Are you sure the container is running right now?
What does:
netstat -an | grep 28967
…show when run on storj1? I’d expect something like this if the node is online and listening:
So the node is running. The VM can see it attached to the port. The VM says its own firewall has that port open. BUT you can’t “nc” that IP/port from elsewhere on your 192.168.x.y network. But you can ssh in directly… but that’s not open in your storj1 firewall?
How did nc to port 22 even work? Maybe you disabled storj1 ufw for troubleshooting? Whatever - I’m not sure what else could be blocking 28967.
Can you netcat from storj1 locally to itself?
nc -v 127.0.0.1 28967
If that connects… but the external nc can’t… then either the local storj1 ufw is in some weird state… or something it the proxmox layer is blocking it.
You kinda have me stumped. Everything shows Storj is running properly in its container, and the VM can see it, and the VM is obviously generally on the the network (as you can SSH in, and Storj can see the Internet etc). You wouldn’t think anything is wrong at the proxmox layer… as it’s exposing the VM IP and letting you SSH in.
I’m not sure what else can be preventing port 28967 from being exposed to the rest of your 192.168.x.y network (and your router, and it’s port-forwarding rules (that are probably fine)).
If you disable ufw on storj1 (as a test)… does that let you “nc -v 192.168.1.214 28967” from 2024MBA?
If it did… then… I still don’t know: perhaps reboot storj1 once more? If it doesn’t… then… I still don’t know - you could reboot proxmox but I can’t imagine it letting port 22 through and not 28967 unless that’s some default rule. In general you let the VMs run their own firewalls and the hypervisor tries to stay out of the way.
Storjnode was up and running after reboot before nc port check command.
I think its proxmox, ports are open on the VM and router side, only thing between them is proxmox. Not to mention issue started after I updated the kernel and restarted proxmox. I even restored the VM to a backup from last week and no change as well as deleting the storj container and docker run’ing it again.
I wish you luck man: unfortunately I can’t help debug proxmox. But you have done testing on both sides of it, inside and out, and you’ve run out of places that can touch your network in a way that would block that Storj port. The fact that it is letting port 22 through… does feel like a default firewall rule active someplace.
)