Insight for why iOS banking apps won't authenticate through vpn #14308
-
I'm very new to the Algo VPN, but I read a really great article about it and wanted to try it for myself. I set up space on AWS EC2 and deployed Algo to the server using the recipe here in the repo and everything seemed to go perfectly. I set it up on an iphone running iOS 14 with WireGuard and most everything works exactly as expected. The traffic is routing from the Algo server. I can access websites, email, most everything. However, when I try and use a banking app, the authentication fails and says some variation of "the login service isn't available". This happens on different apps (banking, credit card, etc). I've not seen this behavior when I use a commercial VPN service and I'm wondering if I didn't configure something correctly or I need to make some adjustment. I appreciate any advice or insight. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 9 replies
-
You will certainly encounter sites that block access from cloud provider networks, but in my experience fewer sites block access from AWS and I don't personally have issues with my banking or credit card apps when using Amazon Lightsail. Did you deploy Algo with DNS adblocking? Perhaps that's getting in the way. You can easily test this by changing the DNS setting in the WireGuard app. Make a note of the current value for DNS and change it to 8.8.8.8. Your DNS requests won't be encrypted upon leaving your AlgoVPN with this change, but you can quickly determine if Algo's DNS adblocking is causing your problems. |
Beta Was this translation helpful? Give feedback.
You will certainly encounter sites that block access from cloud provider networks, but in my experience fewer sites block access from AWS and I don't personally have issues with my banking or credit card apps when using Amazon Lightsail.
Did you deploy Algo with DNS adblocking? Perhaps that's getting in the way. You can easily test this by changing the DNS setting in the WireGuard app. Make a note of the current value for DNS and change it to 8.8.8.8. Your DNS requests won't be encrypted upon leaving your AlgoVPN with this change, but you can quickly determine if Algo's DNS adblocking is causing your problems.