Help: new website json content importer does not work anymore

Hi,

the errormessage at
https://www.sensorwebhub.org/?page_id=11557
is a tieout after 5 seconds.

You can increase this value by adding
urlgettimeout=NO_IN_SEC to the shortcode.
And debugmode=10 to see some debug-info.

But this does not adress the basic problem: Maybe the API-JSON-feed answers very slow. Maybe due to too much data (too big) or a slow API-server or a slow internet-connection between your server and the API-server.

What is the API-JSON-url?

Bernhard

Hi Bernhard,
sorry for replying late.

The urlgettimeout did not work.
the url is https://149.139.16.96:8080/swb2-2/j_get_station_sum?macrotipo=M and it works.

The debug mode shows the following informations:

DEBUG: Cache is active
DEBUG: try to retieve https://149.139.16.96:8080/swb2-2/j_get_station_sum?macrotipo=M
DEBUG: wp_remote_get to https://149.139.16.96:8080/swb2-2/j_get_station_sum?macrotipo=M
DEBUG: arguments: Array ( [timeout] => 5 )
Something went wrong fetching URL with JSON-data: cURL error 28: Connection timed out after 5000 millisecondsDEBUG: error getting URL: cURL error 28: Connection timed out after 5000 milliseconds
error: get of json-data failed – plugin aborted: check url of json-feedDEBUG: no data received: check url of json-feed
DEBUG: api-answer:

DEBUG: basenode:
DEBUG: template:
{numero}
problems with JSON-structure: check basenode-param

Thanks for help!

Hi,

see https://wptest.kux.de/149-139-16-96/
Done by this:

[jsoncontentimporter url=https://149.139.16.96:8080/swb2-2/j_get_station_sum?macrotipo=M debugmode=10]numero: {numero}[/jsoncontentimporter]

This is working on my server.
As the error is “Connection timed out after 5000 milliseconds” this might mean, that your Server can’t connect https://149.139.16.96:8080 for some reason.

Can you ask your hoster or webserver-techie what might be the reason:
php-curl is trying via wp_remote getting something from https://149.139.16.96:8080

Bernhard

Hi Bernhard,
thank you so much for your detailed reply.
The strange thing is that also in the previous deployment hosted on another server started to do the same after a while.
I will check again.

Thank you for your help.

Elena