Why does HTTPCaller send errors on FME-server

Hello,

 

Can you reach the URL  'https://api.meldingen.utrecht.nl/signals/v1/private/csv'  from FME Flow (Server) Core host machine in a web browser or in a tool like Postman? If not, then there may be network issue, like a missing or incorrect proxy configuration or firewall rules interfering.

If yes, you might need to import the endpoint's [ 'https://api.meldingen.utrecht.nl/signals/v1/private/csv'] SSL/TLS certificate into Trusted cacerts on the FME machine so that FME Flow trusts it.

 

Hi Merline, Few checks have been done on our FME server core host: The URL is available through a browser: (no token presented so HTTP 401) [cid:image001.png@01D9E0C3.985BFC30] Certificate from “meldingen.utrecht.nl” has been added to the FME server core host al long time ago: [cid:image002.png@01D9E0C3.985BFC30] [cid:image003.png@01D9E0C3.985BFC30] The -CA from this website is trusted in Windows and in "D:\\Program Files\\FMEServer\\Utilities\\jre\\lib\\security\\cacerts" Given the partial download and http 200 this tells me that connectivity or certs are not the issue Some history: this workflow/download used to work fine until mid July when we started seeing errors with the attempts to downloads. From 14 – 31 july we saw more and more Error-logs (not all attempts) coming with this message: 2023-07-14 06:15:09| 0.3| 0.1|INFORM|HTTPCaller (HTTPFactory): [1]: Starting HTTP download from 'api.meldingen.utrecht.nl'. Expected transfer size: 48.44 MB 2023-07-14 06:15:36| 0.8| 0.5|INFORM|HTTPCaller (HTTPFactory): [1]: HTTP Download: received 10.31 MB 2023-07-14 06:16:04| 1.3| 0.5|INFORM|HTTPCaller (HTTPFactory): [1]: HTTP Download: received 20.41 MB 2023-07-14 06:16:32| 1.8| 0.5|INFORM|HTTPCaller (HTTPFactory): [1]: HTTP Download: received 30.51 MB 2023-07-14 06:17:00| 2.2| 0.4|INFORM|HTTPCaller (HTTPFactory): [1]: HTTP Download: received 40.61 MB 2023-07-14 06:17:18| 2.7| 0.5|INFORM|HTTPCaller (HTTPFactory): [1]: HTTP transfer summary (api.meldingen.utrecht.nl): status code: 200, download size: 49639424 bytes, DNS lookup time: 12 ms, total transfer time: 130505 ms 2023-07-14 06:17:18| 2.7| 0.0|ERROR |HTTPCaller (HTTPFactory): [1]: HTTP transfer error: Stream error in the HTTP/2 framing layer 2023-07-14 06:17:18| 2.7| 0.0|ERROR |HTTPCaller (HTTPFactory): [1]: Please ensure that your network connection is properly set up 2023-07-14 06:17:18| 2.7| 0.0|ERROR |HTTPCaller (HTTPFactory): [1]: No proxy settings have been entered. If you require a proxy to access external URLs, please ensure the appropriate information has been entered 2023-07-14 06:17:18| 2.7| 0.0|ERROR |HTTPCaller (HTTPFactory): An error occurred while accessing the URL 'https://api.meldingen.utrecht.nl/signals/v1/private/csv' 2023-07-14 06:17:18| 2.7| 0.0|FATAL |The below feature caused the translation to be terminated 2023-07-14 06:17:18| 2.7| 0.0|STATS |Storing feature(s) to FME feature store file `\\\\domstad\\aplroot$\\APLDATA\\FMESERVER\\resources\\logs\\engine\\current\\jobs\\4000\\job_4556_log.ffs' That changed in august when we saw the error logs switching to the message I already sent: 65 2023-9-4 13:06:56 | HTTPCaller (HTTPFactory): [1]: HTTP Download: received 40.00 MB 66 2023-9-4 13:07:19 | HTTPCaller (HTTPFactory): [1]: HTTP transfer summary (api.meldingen.utrecht.nl): status code: 200, download size: 52183040 bytes, DNS lookup time: 4 ms, total transfer time: 120111 ms 67 2023-9-4 13:07:19 | HTTPCaller (HTTPFactory): [1]: HTTP transfer error: Transferred a partial file 68 2023-9-4 13:07:19 | HTTPCaller (HTTPFactory): [1]: Please ensure that your network connection is properly set up 69 2023-9-4 13:07:19 | HTTPCaller (HTTPFactory): [1]: No proxy settings have been entered. If you require a proxy to access external URLs, please ensure the appropriate information has been entered 70 2023-9-4 13:07:19 | HTTPCaller (HTTPFactory): An error occurred while accessing the URL 'https://api.meldingen.utrecht.nl/signals/v1/private/csv' 71 2023-9-4 13:07:19 | The below feature caused the translation to be terminated 72 2023-9-4 13:07:20 | Storing feature(s) to FME feature store file `\\\\domstad\\aplroot$\\APLDATA\\FMESERVER\\resources\\logs\\engine\\current\\jobs\\7000\\job_7447_log.ffs' 73 2023-9-4 13:07:20 | +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Would this help you finding a solution? Kind regards, Met vriendelijke groet, Gerro Zegeling, Senior Specialist Ruimtelijk Informatie Gemeente Utrecht DomstadIT Voorziening Data Team Ruimtelijke Informatie Postadres Postbus 16200, 3500 CE Utrecht Bezoekadres Stadsplateau 1, 3521 AZ Utrecht Telefoon 06-43835421 E-mail g.zegeling@utrecht.nl Internet www.utrecht.nl<http://www.utrecht.nl/> Aanwezig ma - vr

Hi,

 

We have set up a workaround by downloading to a local disk on our FME-server machine. There seemed to be an issue writing data to the network share we used to which connection was instable.

 

All is well now.