Page 1 of 2
3rd party http not working - CMX release 3.14.0 build 3159 - Win7 [solved]
Posted: Sat 04 Dec 2021 8:38 pm
by Gyvate
Hi
after installing the 3159 build, my 3rd party http posting stopped working
Downgraded again to 3152 where it works properly again.
attached the MXDiags file
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 12:33 am
by HansR
Windows NT 6.1 reached its end of support at
14 jan 2020 so apparently the HTTPclient feature does not seem to be working anymore because of the upgrade to .NET 4.8 (which is apparent from a later date).
Similar behaviour can probably be observed on Windows 7 with the same reason.
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 7:13 am
by meteo19
HansR wrote: ↑Sun 05 Dec 2021 12:33 am
Windows NT 6.1 reached its end of support at
14 jan 2020 so apparently the HTTPclient feature does not seem to be working anymore because of the upgrade to .NET 4.8 (which is apparent from a later date).
Similar behaviour can probably be observed on Windows 7 with the same reason.
Hi Hans
Update to 3.14.0 (build: 3159) with Microsoft Windows 7 Pro and everything works normally since 2h30 now. To see tonight at midnight but for the moment everything is fine.
Regards;
Patrick
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 10:19 am
by HansR
meteo19 wrote: ↑Sun 05 Dec 2021 7:13 am
HansR wrote: ↑Sun 05 Dec 2021 12:33 am
Windows NT 6.1 reached its end of support at
14 jan 2020 so apparently the HTTPclient feature does not seem to be working anymore because of the upgrade to .NET 4.8 (which is apparent from a later date).
Similar behaviour can probably be observed on Windows 7 with the same reason.
Hi Hans
Update to 3.14.0 (build: 3159) with Microsoft Windows 7 Pro and everything works normally since 2h30 now. To see tonight at midnight but for the moment everything iby s fine.
Regards;
Patrick
Hi Patrick,
Yes, but you have a Davis which is not read through the HTTP protocol.
You may get an issue with your extra sensors though (which are ECOWITT if they are handled by the HTTP protocol or no issue when differently, so far that seems OK).
And still: you are not on the CUtils map which is on .NET 4.8 much longer and which uses HTTPclient for handling the signature files and map download.
Regards,
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 11:25 am
by mcrossley
HansR wrote: ↑Sun 05 Dec 2021 12:33 am
Windows NT 6.1 reached its end of support at
14 jan 2020 so apparently the HTTPclient feature does not seem to be working anymore because of the upgrade to .NET 4.8 (which is apparent from a later date).
Similar behaviour can probably be observed on Windows 7 with the same reason.
Hi Hans, where have you got this information from. As far as I know Framework 4.8 is fully functional on Windows 7 SP1 and later?
I'll check that the Custom HTTP upload - but it will on the Windows 11 that my dev machine runs...
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 12:42 pm
by Gyvate
@Mark:
on Win11 it works - but on Win7 which is my main Windows CMX server it does not.
There are indications pointing to certificates and trusted connections coming with the .NET "library".
Maybe some special .NET runtime (and/or SDK) needs to be installed on the Win7 machine and then some dotnet commands issued.
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 12:46 pm
by mcrossley
I do not think so - do you have the latest version of the 4.8 runtime installed? -
https://dotnet.microsoft.com/download/d ... work/net48
Edit: and up to date with Windows updates?
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 12:59 pm
by mcrossley
Could you capture the actual error messages you are see relating to Framework please?
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 1:17 pm
by Gyvate
nothing revealing in the MXdiags -
2021-12-04 22:17:59.021 CustomHttpSeconds: Querying -
https://api.weatherwizz.com/api/update?stationid=.............
2021-12-04 22:17:59.619 CustomHttpSeconds: An error occurred while sending the request.
keeps on repeating
I only did some google digging and ran e.g. into threads/posts like
https://www.hannesholst.com/blog/httpcl ... e-request/
and
https://gateway.sdl.com/apex/communityk ... =000015928
will install the .NET 4.8 runtime and see if there are any changes
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 1:24 pm
by mcrossley
OK, that second link may be a clue.
In the previous versions of MX I explicitly enabled TLS 1.1 and 1.2.
With .Net 4.8 the recommendation is not to do this, and let the .OS decide what is available, this allows your client to use TLS 1.3 where it is available.
So that reg hack, which enables TLS 1.2 by default in Windows 7 maybe worth investigating.
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 1:38 pm
by HansR
mcrossley wrote: ↑Sun 05 Dec 2021 11:25 am
Hi Hans, where have you got this information from. As far as I know Framework 4.8 is fully functional on Windows 7 SP1 and later?
I'll check that the Custom HTTP upload - but it will on the Windows 11 that my dev machine runs...
Hi Mark,
I have this from the experience (with CUtils) that NET 4.8 has issues on Win7 and now apparently on NT 6.1. Both are apparently not supported anymore so I presume the required .NET updates do not come automatically (if installable at all). I have no documentation for you. All issues experienced are with the
and the
calls. No other problems seen.
And yes, they are to https sites but I don't do any forced settings - I think - so if you are right the system should find its way.
Could there be an interference with FluentFTP setting of TLS, or SSH for that matter?
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 3:08 pm
by Gyvate
(re-)installed .NET 4.8 - went back to 3159.
Must have been a re-install as the installation routine insisted on a repair => 4.8 is already on Win7
(even though since January 2020 there are no updates anymorefor Win7, except for the Virus Scanner).
But - no change.
On my Win11 installation, I keep on getting the following message for each post:
2021-12-05 16:00:42.675 CustomHttpSeconds: Querying -
https://api.weatherwizz.com/api/update?stationid=......
2021-12-05 16:00:42.977 CustomHttpSeconds: Response status code does not indicate success: 400 (Bad Request).
However, the post goes through and the data arrives.
(Win11 = 10.0.22499.1010)
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 3:28 pm
by Mapantz
Gyvate wrote: ↑Sun 05 Dec 2021 3:08 pm
(re-)installed .NET 4.8 - went back to 3159.
Must have been a re-install as the installation routine insisted on a repair => 4.8 is already on Win7
(even though since January 2020 there are no updates anymorefor Win7, except for the Virus Scanner).
But - no change.
On my Win11 installation, I keep on getting the following message for each post:
2021-12-05 16:00:42.675 CustomHttpSeconds: Querying -
https://api.weatherwizz.com/api/update?stationid=......
2021-12-05 16:00:42.977 CustomHttpSeconds: Response status code does not indicate success: 400 (Bad Request).
However, the post goes through and the data arrives.
(Win11 = 10.0.22499.1010)
I was getting problems with weatherwizz over a month ago - same error messages. It was working fine & dandy, then suddenly I started getting those messages. I hadn't upgraded CMX, and nothing had changed on Windows 10. It was definitely an issue on weatherwizz's side.
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 3:35 pm
by Gyvate
Mapantz wrote: ↑Sun 05 Dec 2021 3:28 pm
Gyvate wrote: ↑Sun 05 Dec 2021 3:08 pm
(re-)installed .NET 4.8 - went back to 3159.
Must have been a re-install as the installation routine insisted on a repair => 4.8 is already on Win7
(even though since January 2020 there are no updates anymorefor Win7, except for the Virus Scanner).
But - no change.
On my Win11 installation, I keep on getting the following message for each post:
2021-12-05 16:00:42.675 CustomHttpSeconds: Querying -
https://api.weatherwizz.com/api/update?stationid=......
2021-12-05 16:00:42.977 CustomHttpSeconds: Response status code does not indicate success: 400 (Bad Request).
However, the post goes through and the data arrives.
(Win11 = 10.0.22499.1010)
I was getting problems with weatherwizz over a month ago - same error messages. It was working fine & dandy, then suddenly I started getting those messages. I hadn't upgraded CMX, and nothing had changed on Windows 10. It was definitely an issue on weatherwizz's side.
maybe the "Response status code does not indicate success: 400 (Bad Request)" message is a weatherwizz issue, but the "An error occurred while sending the request" message with no data sent rather not. The same message sent inside the same network, one on a Win7 machine and one on a Win11 machine, Win11 successful, Win7 unsuccessful, doesn't really point at weatherwizz imo.
Re: 3rd party http not working - CMX release 3.14.0 build 3159
Posted: Sun 05 Dec 2021 4:21 pm
by mcrossley
Have you tried applying that registry update to the Windows 7 machine and rebooting it, then trying v3.14 again?