Hi, Have moved all data to Ubuntu docker , seems dockers stars fine, dashboard visible and accessible from outside, but shows OFFLINE . Logs show repeating errors, that cannot contect sattelite. Both ports are forwarded well (EdgeOS), [image] Dashboard access from outside well [image] Docker i…

I’m not a Ubuntu user but isn’t ufw turned on by default so you have to open necessary ports in ufw ? or simply turn ufw off … " By default, UFW is set to **deny all incoming connections and allow all outgoing connections."

nop, no UFW at all. all disabled, iptables clean. weird thing 14002 port works fine . but storj main port, is not accessible from any other IP other than 127.0.0.1

[image] bitomatas: but storj main port, is not accessible from any other IP Try these troubleshooting steps. [image] My Node is OFFLINE for 2 hours FAQ It should connect in seconds. There are a few things you should check. Start with checking the port. On https://…

The port forward is correctly configured, as i have windows running properly , and linux 14002 port is acessible ok. I think there might be issue with identity, as i copied files form windows. Is there a way to check those ? My Node is OFFLINE for 2 hours docker exec -it storagenode ls -l /app…

Did you check the yougetsignal page nerdatwork mentioned? It says 28967 is closed to you (checked at around 9am EST - You missed a 7x.xx.xxx.x.0 edit above :wink: )

i know that it is not opened. the problem is it is not opened not from outside, but from inner network it is not accessibel as well. seems like dahsboard 14002 loads webb, but main funtionality on 28967 is not, as i cannot telnet from local net . And i ran out of ideas what to check :frowning: The o…

I don’t understand what problem you’re trying to solve. The “ping satellite: failed to ping storage node” error in your log is indicating a connection from outside is failing to make it in: there’s no part of Storj that will be talking to your node from your LAN. Or does the node work 100% OK when …

Apparmor could be the culprit so you can read :point_down: [image] Can't stop container - permission denied troubleshooting Yes, it’s a security system on top of usual linux permissions that enforces access control rules on what users and programs can access what resources…

Now i have a small progress - when i created config.yaml manually inside the docker and restarted, seems the port became accessible from outside, so i see now externally: { “Statuses”: null, “Help”: “To access Storagenode services, please use DRPC protocol!”, “AllHealthy”: true } This is weird…

OK , if anyone has any ideas why my dashboard could be showing me OFFLINE I would appreciate :slight_smile: tried playing with IP swithching to 0.0.0.0 , 192.168.1.166 - rmeoving at all keeping only :port seems like not working. Is there any kind of special log i can trace for dashboard ? [imag…

Windows to Ubuntu move went wrong: docker ping error on starting

Node Operators troubleshooting

nerdatwork January 5, 2025, 1:22pm 4

Try these troubleshooting steps.