Cannot connect to satellite

[baont]

Hello everybody,
My node has been offline this morning, i check my port forwarding but it work fine port 28968 still forwad to my node but some how my node is offline.
Here are some of my log , please help.

2023-12-22 02:34:32.983421+00:002023-12-22T09:34:32+07:00	ERROR	contact:service	ping satellite failed 	{"process": "storagenode", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "attempts": 10, "error": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 171.224.81.80:28967: connect: no route to host", "errorVerbose": "ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 171.224.81.80:28967: connect: no route to host\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:209\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:157\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
2023-12-22 02:36:30.240325+00:002023-12-22T09:36:30+07:00	WARN	console:service	unable to get Satellite URL	{"process": "storagenode", "Satellite ID": "12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo", "error": "console: trust: satellite is untrusted", "errorVerbose": "console: trust: satellite is untrusted\n\tstorj.io/storj/storagenode/trust.init:29\n\truntime.doInit1:6740\n\truntime.doInit:6707\n\truntime.main:249"}
2023-12-22 02:36:30.250471+00:002023-12-22T09:36:30+07:00	WARN	console:service	unable to get Satellite URL	{"process": "storagenode", "Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB", "error": "console: trust: satellite is untrusted", "errorVerbose": "console: trust: satellite is untrusted\n\tstorj.io/storj/storagenode/trust.init:29\n\truntime.doInit1:6740\n\truntime.doInit:6707\n\truntime.main:249"}

many thanks.

[nerdatwork]

Try this checklist

My Node is OFFLINE for 2 hours

It should connect in seconds. There are a few things you should check. Start with checking the port. On https://www.yougetsignal.com/tools/open-ports/?port=28967 you can fill in the domain or IP you are using in the run command. Then check the port. If it’s closed, it could still be several things. Make sure the WAN IP you see in your router settings matches the IP shown on the above page. Make sure your port forward is set up correctly. That means no filter on incoming IPs, forwarding to th…

[baont]

Hi thanks for your fast reply,
Here is my port check result, my domain is truenas.netstorages.com and port 28967 is still foward to my node. But somehow my node still offline

[nerdatwork]

@baont

fine port 28968 still forwad to my node

Are you sure you are checking the correct port ?

[baont]

@nerdatwork

ou are checking the correct por

sorry my mistake port 28967 is forward to my node and still open.

here is my cert file, it seem like my cert file is ok, but my node still offline

[bre]

The ip address in the satellite error 171.224.81.80:28967
and the ip address for the domain you are checking are not the same.

truenas.netstorages.com has address 58.187.170.71

[baont]

thanks for your reply,
so how do i fix it, i don’t have static ip address :v my public ip now is 58.187.170.71

[arrogantrabbit]

You don’t have static IP or you dont have public IP?

In the latter case:

• ask your ISP for a public IP, or
• use VPN with port forwarding at a nearby datacenter

In the former — you don’t need static IP. You can use DDNS to keep a FQDN record up to date with your current IP

[Alexey]

You need to run a DDNS updater for the host truenas.netstorages.com, it’s better to configure it on your router (prefferrably), but you may also run an application from your DDNS provider on the TrueNAS Scale server.

[baont]

I rent the domain netstorages.com and i have an DDNS updater on my truenas, as it turnout the IP “171.224.81.80” is my yesterday public IP, to day my ip change to “58.187.170.71”. My DDNS updater still update new IP for my domain but satellite still ping to my old IP (171.224.81.80).
So can you help me with this situation.
Thanks

[arrogantrabbit]

What do you have in the configuration file/docker command for contact.external-address?

Also, ttl of your ddns record is 5 minutes — so for up to 5min after change the fqdn may be resolving to your old address

[baont]

Thanks for all your supports,
I have found the solution, it turn out it all my fault I’m using an app from Truechart and in the address field i put in baont.ddns.net.

It was before i can rent a domain netstorages.com.
The DDNS updater was not update new ip for the “baont.ddns.net” that why my node offline.
Thanks for all you guys support