Ambientweather network drops support for HTTPS SSL uploads and now enforces TLS -> needs Meteobridge 4.1 or newer

[admin]

Some Meteobridge users of the ambientweather network reported problems to feed data to there since April 1, 2020. Reason behind this is that ambient decided to have their server no longer supporting SSL HTTPS connections, only TLS. Meteobridges before version 4.1 do not support HTTPS uploads via TLS so these Meteobridge versions cannot upload to ambientweather network anymore.

Ambient points to security reasons for doing so (https://help.ambientweather.net/help/we ... il-1-2020/), which is a valid argument when it comes to web pages and user interfaces in general. Meteobridge directs the ambientweather data upload to a distinct URL endpoint. Unfortunately, the TLS enforcement seems to cover the whole domain, so that the data upload endpoint is also impacted.

When you are running version 4.1 or newer on your Meteobridge you should be fine as TLS 1 support is included since version 4.1. If you are on an older version you will need to update to a newer version.

[lrosenman]

I'm on 4.3 (Meteobridge 4.3 (Mar 27 2020, build 13442), FW 1.3) and still getting:
Ambient Weather Network: 2020-04-06 20:20:28 Error: 2020-04-06 20:20:26 OpenSSL: error:14077410:lib(20):func(119):reason(1040) Unable to establish SSL connection. (no more tries)

Screen Shot 2020-04-06 at 8.22.07 PM.png (138.08 KiB) Viewed 2676 times

Screen Shot 2020-04-06 at 8.22.47 PM.png (40.85 KiB) Viewed 2676 times

[admin]

That is because you are on the DIR-505 platform, which is very rare (and not sold by Ambientweather) and might have been overlooked when doing the TLS wget update with version 4.1. I will put it on my todo list.

[admin]

Just released Meteobridge version does fix this for DIR-505 platform as well.

[lrosenman]

Thank You.