-
Notifications
You must be signed in to change notification settings - Fork 118
VPN not working after iOS 14 upgrade #25
Comments
@jgimenez - (I hope tagging directly is ok) Going through the README, I found the troubleshooting link: https://github.com/hwdsl2/setup-ipsec-vpn/blob/master/docs/clients.md#troubleshooting where it mentioned an issue with iOS 13 and changing sha2-truncbug value from yes to no and then doing an ipsec restart. Voila the Iphone VPN connects now. |
If you want to apply the change just for the container you are running, you can edit the |
Another fix would be to just use Cisco IPSEC instead of L2TP over IPSEC |
Please feel free to send PRs if you want to support additional devices. However, iOS 14 and iOS 15 both work for me with no further changes. |
Hi,
Thanks so much for this wonderful and amazing project, have been using it for 2 years.
I'm very new to github so please excuse if I say or ask something stupid.
I'm running the "docker-ipsec-vpn-server" in a cloud hosting environment and use it mainly for 4-5 personal phones.
After the iOS 14 upgrade, the VPN does not connect on iPhone, although Android phones work fine. It looks like the issue is mentioned here: https://developer.apple.com/forums/thread/660499. It talks about deactivating SHA-256 compatible mode (96 bits). After searching and reading on various places online I found that these parameters may be defined in ipsec.conf. I found 2 ipsec.conf files in the container environment:
These are both identical and contain the following which could be relevant:
ike=3des-sha1,3des-sha2,aes-sha1,aes-sha1;modp1024,aes-sha2,aes-sha2;modp1024,aes256-sha2_512
phase2alg=3des-sha1,3des-sha2,aes-sha1,aes-sha2,aes256-sha2_512
sha2-truncbug=yes
But I have no idea what to change and in which of the 2 files to change.
I would be more than happy to contribute and help others as I know many people would be facing this issue, but need some initial help in figuring out.
I would really appreciate if you can provide some help.
Thanks again.
The text was updated successfully, but these errors were encountered: