<%= heading %>
<% } %>-
<% blocks.forEach(function(block, index) { %>
-
<% if (imageHeight) { %>
<% } %>
<% if (!block.description) { %> <%= block.name %> <% } else { %> <%= block.name %> <% } %>
<% if (block.description) { %> <% } %>
<% }) %>
Comments
4 comments
Hello Timothy,
Thank you for your feedback—we appreciate you taking the time to share your experience, and we’re sorry for the difficulty you encountered. In many cases, in-flight Wi-Fi networks restrict VPN connections, which can commonly cause issues for iOS users. That said, it’s possible you experienced a different underlying issue.
We’ll be sure to pass your suggestion along to our development team for further review. If you’d like help troubleshooting or need additional support, please feel free to contact our Member Care team at support@covenanteyes.com—we’d be happy to assist.
Thank you again for reaching out and have a great day!
Hello Vanderark.
Thank you for your question. While I haven't heard of any issues specifically for the wifi on American Airlines it is possible that their wifi has its own filter in place that may conflict with our own. I do have a couple of suggestions to try to get through that wifi portal.
First, try restarting your phone. As soon as it is up and usable try connecting to the airplane wifi. Second, if feasible, try disabling the filtering on your account temporarily and then refresh the Covenant Eyes app on your phone. Doing so should remove any potential filtering conflicts.
I hope you find these suggestions helpful and I do apologize about the hassle. Thank you and have a great day.
I also encountered this problem. It appears to be due to the Victory Shield app ignoring and overriding the DNS server provided by the American Airlines captive portal. iOS is then unable to load the captive portal page aainflight.com because it is not available in public DNS, but only within the DNS provided within the captive portal network.
Perhaps Victory Shield should be updated to detect if the device is in a captive portal and use the system DNS until it is no longer in the captive portal.
Yes, I have had this issue on a recent AA flight. The in flight wifi did not work and the captive portal was unable to load.
Please sign in to leave a comment.