Very few VPN endpoints online

Product support
1

We have been having issues with VPN connections lately. This is the results from a DNS lookup of vpn.balena-cloud.com

vpn.balena-cloud.com.   120     IN      CNAME   a85143ac6d69f41018a7b869e341f7ed-15bc7adf7609a5ca.elb.us-east-1.amazonaws.com.
a85143ac6d69f41018a7b869e341f7ed-15bc7adf7609a5ca.elb.us-east-1.amazonaws.com. 60 IN A 52.44.207.231
a85143ac6d69f41018a7b869e341f7ed-15bc7adf7609a5ca.elb.us-east-1.amazonaws.com. 60 IN A 34.198.122.176
a85143ac6d69f41018a7b869e341f7ed-15bc7adf7609a5ca.elb.us-east-1.amazonaws.com. 60 IN A 52.54.239.189
a85143ac6d69f41018a7b869e341f7ed-15bc7adf7609a5ca.elb.us-east-1.amazonaws.com. 60 IN AAAA 2600:1f18:6600:7f01:3e6b:5dfd:7b7:b73a
a85143ac6d69f41018a7b869e341f7ed-15bc7adf7609a5ca.elb.us-east-1.amazonaws.com. 60 IN AAAA 2600:1f18:6600:7f02:8174:aacd:643b:b985
a85143ac6d69f41018a7b869e341f7ed-15bc7adf7609a5ca.elb.us-east-1.amazonaws.com. 60 IN AAAA 2600:1f18:6600:7f00:ba4c:47b5:c865:46a4

I note that most of these hosts are offline, both from our network and a third part network (refused connection).

Looking at newer generated configs it looks like you are transitioning away from this DNS name and towards cloudlink.balena-cloud.com. Some of us with older fleets are still very much using the older DNS name.

How about CNAME’ing it so older fleets do not get obliterated?

We will be doing a fleet update soon to update our HostOS but please be better.

2

I am now aware of the blog post.

Fortunately like the blog post states os-config fixes all active hubs. Its our flasher that this was noticed on.

We will put an issue out to somehow subscribe to the blog posts for such updates. Perhaps balena could publish a critical updates feed of some kind though? e.g email or via github…