[Solved] json via curl no longer works on stretch

Harry van der Wolf

Running shell scripts on pimatic 0.9.45 on a freshly updated jessie to stretch rpi, suddenly no longer work.

Commands like
curl -s -X PATCH --header "Content-Type:application/json" --data '{"type": "value", "valueOrExpression": "'$NEWTIME'"}' --user "$USERNAME:$PASSWORD" $URL/$VARNAME
or
curl -s -X PATCH --header "Content-Type:application/json" --data '{"type": "value", "valueOrExpression": "'$oprittemperatuur'"}' --user "$USERNAME:$PASSWORD" $URL/oprit-temperatuur
suddenly no longer work on Debian stretch.

Reported error:
json: error: input is not JSON: Unexpected '<' at line 1, column 1: <html> ^
Someone any idea?

mwittig

@harry-van-der-wolf said in json via curl no longer works on stretch:

Someone any idea?

Works for me

TEMPVAL=40
curl -s -X PATCH --header "Content-Type:application/json" --data '{"type": "value", "valueOrExpression": "'$TEMPVAL'"}' --user XXX:XXX localhost/api/variables/temp

I think I have the latest updates for stretch installed.
Curl version on my systems is as follows:

pi@raspberrypi:~ $ curl -V
curl 7.52.1 (arm-unknown-linux-gnueabihf) libcurl/7.52.1 OpenSSL/1.0.2q zlib/1.2.8 libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL

Harry van der Wolf

Thanks,

I have exactly the same version with the same protocols and features.
But it still doesn’t work

mwittig

@harry-van-der-wolf Which value do you have for $URL? I assume it is <hostname>/api/variables, right? Did you also try to execute the curl commands directly in the bash shell? Possibly it is something else in your shell scripts which broke by the upgrade. To investigate this further it might help to trace the shell scripts to see exactly each line as it is executed (after expansions have been performed), e.g. use bash -xto execute the script.

Harry van der Wolf

So stupid!

I changed http ports of the nginx webserver and the node/pimatic webserver. I switched the node/pimatic server from 80 to 9001 and vice versa. I changed php scripts and config for nginx, but forgot to update the scripts for pimatic. After having added the port to the url in the scripts it worked fine.

mwittig

@harry-van-der-wolf said in [Solved] json via curl no longer works on stretch:

So stupid!

No worries. It is great you managed to solve the issue!
When I wrote my previous had in in mind that you may have a proxy in the loop, but I forgot to ask about this.