It’s not uncommon for IP addresses to change after an outage, even if they’re normally static. Double check your external and internal IP address. If the external address is changed, update your run command and recreate your container. If the internal address has changed, update your port forwards.
This is assuming you used a static IP in the run command, if you used a domain, update the DNS record. If you used DDNS, make sure the update client is running and updating your IP.
I have double checked everything in that FAQ a couple of times.
Everything is set up as it should be.
Still getting the “ERROR contact:chore ping satellite failed” message.
It looks like the errors started becoming MORE frequent when 0.26.2 was released. Before that it was a one or 2 times a day, then after the update it was a few times an hour till the 26th (first outage) then it was multiple blocks of errors every few hours, til last nights outage, then it was constant errors.
docker exec -it storagenode ping -c4 satellite.stefan-benten.de
PING satellite.stefan-benten.de (184.108.40.206): 56 data bytes
64 bytes from 220.127.116.11: seq=0 ttl=49 time=93.025 ms
64 bytes from 18.104.22.168: seq=1 ttl=49 time=105.079 ms
64 bytes from 22.214.171.124: seq=2 ttl=49 time=85.705 ms
64 bytes from 126.96.36.199: seq=3 ttl=49 time=105.156 ms
— satellite.stefan-benten.de ping statistics —
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 85.705/97.241/105.156 ms
Unfortunately we can’t determine where is the issue, i think it ISP problem or DNS issue, but at this moment evryting working fine… I can reccoment setup simple free monitoring by you external ip and node port on uptime robot.
Think I’ll just shutdown the server for a bit and do some maintenance.
Was going to move the node to a new server at the weekend, (end of the month) but might just so that tonight and see if that makes a difference.