Hey everyone, good news, I've managed to fix this issue on my side. However, if I say that I'm okay with the risks, it opens the correct site (looks like it sends 'Host:' header with correct domain afterwards). I've checked it connection with developer tools to my Safari and it shows that connection is TLS1.3 but certificate is for wrong domain. ![]() I first thought that maybe it's because Apple rejected to work with SNI when encryption protocol is lower than TLS1.3, I've enabled TLS1.3, but it didn't help. ![]() ![]() If you want, Matt, I can email you few domains to reproduce the issue if you want to check this from your side. It's not just me, my colleagues and other visitors reporting the same issue with these sites. I've checked and it looks like it's default SSL certificate that I have on my server, but iOS should send SNI before initiating SSL connection to make sure it works with the right certificate, which is not happening. Everything works fine when I open these sites from PC, however when I open some websites from iOS 14 device it shows up error with certificate. ![]() I have a server with nginx and some virtual hosts on it and using different SSL certificates. I've just run into same issue, I've run some tests and it looks like after upgrade to iOS 14 both Safari and Chrome browsers does not support SNI anymore.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |