I have one device out of 150 which are all in the same network which won’t update. It has VPN but no API activity (broken heart). The other device in the same app which is on the same switch has updated.
journalctl -u resin-supervisor --no-pager shows that the device initially cannot resolve api.balena-cloud.com but later it is OK and when I log in via ssh to the host it also works.
The only difference I could find is that the broken device resolves
188.8.131.52 whereas the other one resolves to
184.108.40.206. Both are valid ips for that address:
host api.balena-cloud.com api.balena-cloud.com is an alias for resin-d-alb-15sj6u7hs9afn-1069262607.us-east-1.elb.amazonaws.com. resin-d-alb-15sj6u7hs9afn-1069262607.us-east-1.elb.amazonaws.com has address 220.127.116.11 resin-d-alb-15sj6u7hs9afn-1069262607.us-east-1.elb.amazonaws.com has address 18.104.22.168