on 13-04-2023 18:59
Hello!
Right… I had an iPhone 14 plus and it worked fine. Went into the 02 store and swapped it for an iPhone 14 pro. Came home and did the necessary to get the phone swapped over… works fine on Wi-Fi but when I leave Wi-Fi I can’t access any banking apps, I can’t access Apple Music, Apple Store or Netflix. I keep getting an SSL can’t get a secure connection error. Pics won’t download on WhatsApp and my number is withheld even though I haven’t set it to withheld. Been back to the 02 store and they have sent further network settings to the phone which say will take 24 hours. The sim has been replaced and so far there is no success. Do new network settings really take up to 24 hours to refresh? The chaps in the 02 store refuse to accept that the phone may be faulty and keep saying it’s a network issue.
Solved! Go to Solution.
on 15-04-2023 14:41
on 15-04-2023 14:41
@Coney1982 Have you asked Apple? Official Apple Support
on 17-04-2023 09:10
on 17-04-2023 09:10
on 17-04-2023 10:57
on 17-04-2023 10:57
Well done @O2Sarah- 😂 and pleased it's now working @Coney1982
Veritas Numquam Perit
on 17-04-2023 11:28
on 17-04-2023 11:28
Thank you for tagging Sarah!
on 29-04-2023 07:25
Hi, I have the same ssl error on my email account and apps but they work on wifi. How did you fix this, please?
on 29-04-2023 07:39
on 29-04-2023 07:39
There isn't an account advisor on now until Monday at 9am and it's @O2nath_ci
Hopefully, He'll be able to help.
Veritas Numquam Perit
on 19-08-2023 13:02
on 19-08-2023 13:02
Did they say what it was? I’m having this issue
on 19-08-2023 15:55
on 19-08-2023 15:55
Somebody here reported that enabling the 18+ website setting fixed that SSL issue for them, @HHoulden93 - info on how to do that here: Guide: O2 Age restriction
Good luck!
on 19-08-2023 16:25
on 19-08-2023 16:25
Really?? I wonder if that will help fix the issue ..
I’ve tried it. See if it helps!
Any reason you can think of why it would?
19-08-2023 16:58 - edited 19-08-2023 16:59
19-08-2023 16:58 - edited 19-08-2023 16:59
Could be some element of the normal web page that is blocked at O2's side, whether intentionally or otherwise - usually some odd bit of style sheet or similar that is hidden in the background - only a packet or transaction trace of you trying to access whatever causes the error would show what...
Did it work, @HHoulden93?