Was on AA120 CDG-JFK and had the same issues. As a previous poster said, it has to do with Gogo's network management practices. In order to know what you are doing and manage their bandwidth, they must insert a device mid-stream to decrypt, inspect, then re-encrypt your traffic. Your device recognizes that the SSL encryption certificate it expected is not authentic and raises the error. While you might think you can trust gogo, I would never trust them or anyone else. Understand they can see *all* the traffic in clear text. This means any passwords, usernames, or other confidential information you may be trying to protect with encryption is open for easy reading by them. The same is true for boingo.