Vodafone sudden SSL issues with legacy devices

Forums › One New Zealand (including Vodafone, WxC, Farmside) › Vodafone sudden SSL issues with legacy devices

JonnyCam

643 posts

Ultimate Geek

ID Verified

#253024 22-Jul-2019 11:48

We've got some devices at work which are Android 4.1 & 4.2 which are suddenly not connecting to our servers via the VF sim card,

We are getting an SSL handshake error, which I can only out surmise is attempting to use TLS 1.2 on these devices which don't support it.

This only happens on the VF connection, if I connect to office wifi, and another external connection we have the communications work fine.

Has anyone else noticed anything similar?

Apsattv

2390 posts

Uber Geek

#2281432 22-Jul-2019 14:33

Check the clock/timezone? day date? on them?

JonnyCam

643 posts

Ultimate Geek

ID Verified

#2281553 22-Jul-2019 15:39

Apsattv:

Check the clock/timezone? day date? on them?

Everything seems to be in order, they get their time from the VF server, and check with NTP perodically. (these devices have time sensitive functions)

I've got a found a Spark sim card, and the comms works fine across that.

When I try to use http to access the web services from the legacy device, I'm getting a 502 error (again, only on Vodafone)

mentalinc

3238 posts

Uber Geek

Trusted

#2281577 22-Jul-2019 15:53

What happens when using WIFI to the same services?

CPU: AMD 5900x | RAM: GSKILL Trident Z Neo RGB F4-3600C16D-32GTZNC-32-GB | MB: Asus X570-E | GFX: EVGA FTW3 Ultra RTX 3080Ti| Monitor: LG 27GL850-B 2560x1440

Quic: https://account.quic.nz/refer/473833 R473833EQKIBX

JonnyCam

643 posts

Ultimate Geek

ID Verified

#2281588 22-Jul-2019 16:22

mentalinc:

What happens when using WIFI to the same services?

Works fine on both http & https for our office wifi, an external wifi connection we have, and on a spark sim.

Very strange situation.

Thanks

JonnyCam

643 posts

Ultimate Geek

ID Verified

#2281592 22-Jul-2019 16:37

It just all started working again.

No response to my requests for information from VF, so I am unsure if they fixed this, or it's just 'come right' will be interesting to see if they can provide an explanation.

JonnyCam

643 posts

Ultimate Geek

ID Verified

#2282606 24-Jul-2019 09:18

VF Tech called me, and said this was related to the DNS issues which VF had based on the other thread in the sub forum.

Given this only affected our legacy devices, I'm not sure how this relates, unless they were doing DNS traffic over TLS.

any thoughts?