We have been aware of this for some time but our aging load balancer
didn't support tls1.2
As all browser support 1.0, we have been procrastinating on updating the
load balancer (given the traffic we handle, getting it up and running
with minimum downtime was never going to be easy!)
As it's likely more and more networks will push forward with tls v1.2,
(although why they would actively block 1.0 is strange - it is obsolete
but not insecure per se), as well as other requests on the support
email, we have pushed forward with a new load balancer.
We were able to switch over with no downtime by having both running on
different IPs and switch over to the new one via a DNS switch. That way,
we could iron out any errors as traffic started moving over slowly to
the new LB.
The new LB is now up to ~2.8k requests a second, with the old one
handling ~1k/s at time of writing (the graphs on geoplugin.com
using the new LB, hence the dip) and all issues have been squashed.
Once DNS has been fully propagated (max 24h), you should be able ok.
We flushed the ssl.geoplugin.net
A entry in Google DNS (ssllabs uses
google DNS apparently) and that's now resolving correctly. If your
server uses Google DNS (22.214.171.124), you should also be fine.
We get a shiny "A" badge, which is good enough for us!
> You received this message because you are subscribed to the Google
> Groups "geoPlugin" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to geoplugin+...@googlegroups.com
> To post to this group, send email to geop...@googlegroups.com
> Visit this group at https://groups.google.com/group/geoplugin
> For more options, visit https://groups.google.com/d/optout