Michael von Lipinsky

`[{"id":"e5c0d433.28da38","type":"chatbot-telegram-receive","z":"2cabaefe.e05382","bot":"d44b252a.24f978","botProduction":"","x":200,"y":300,"wires":[["20c9091b.870a16"]]},{"id":"30c87df2.ab4d12","type":"chatbot-telegram-send","z":"2cabaefe.e05382","bot":"d44b252a.24f978","botProduction":"","track":false,"outputs":0,"x":640,"y":320,"wires":[]},{"id":"20c9091b.870a16","type":"chatbot-message","z":"2cabaefe.e05382","name":"","message":[""],"answer":false,"track":false,"x":420,"y":320,"wires":[["30c87df2.ab4d12"]]},{"id":"d44b252a.24f978","type":"chatbot-telegram-node","z":"","botname":"JosiBot","usernames":"","polling":"1000","store":"56baf89d.4bbd88","log":"","parseMode":""},{"id":"56baf89d.4bbd88","type":"chatbot-context-store","z":"","name":"josibot_context","contextStorage":"memory","contextParams":""}]`

... I hope I did the export correctly, never did this before in node-red...

`[{"id":"e5c0d433.28da38","type":"chatbot-telegram-receive","z":"2cabaefe.e05382","bot":"d44b252a.24f978","botProduction":"","x":200,"y":300,"wires":[["20c9091b.870a16"]]},{"id":"30c87df2.ab4d12","type":"chatbot-telegram-send","z":"2cabaefe.e05382","bot":"d44b252a.24f978","botProduction":"","track":false,"outputs":0,"x":640,"y":320,"wires":[]},{"id":"20c9091b.870a16","type":"chatbot-message","z":"2cabaefe.e05382","name":"","message":[{"message":"Hello!"}],"answer":false,"track":false,"x":420,"y":320,"wires":[["30c87df2.ab4d12"]]},{"id":"d44b252a.24f978","type":"chatbot-telegram-node","z":"","botname":"JosiBot","usernames":"","polling":"1000","store":"56baf89d.4bbd88","log":"","parseMode":""},{"id":"56baf89d.4bbd88","type":"chatbot-context-store","z":"","name":"josibot_context","contextStorage":"memory","contextParams":""}]`

Added a text. But this does not change anything, still getting that error in the logs. For me it looks like that the URL is not complete and node is...

No, I can't find any corrupting characters. Did a npm update and restartet node-red. Still the same. ``` Starting as a systemd service. Started Node-RED graphical event wiring tool.. 21...

Sorry to say that this also does work: `[{"id":"9f0f19f5.33fa28","type":"debug","z":"2cabaefe.e05382","name":"","active":true,"console":"false","complete":"true","x":630,"y":560,"wires":[]},{"id":"24851e03.e8ac82","type":"http request","z":"2cabaefe.e05382","name":"","method":"GET","ret":"txt","url":"https://api.telegram.org/botXXXXXXXXXXXXXXXX/getUpdates","tls":"","x":450,"y":560,"wires":[["9f0f19f5.33fa28"]]},{"id":"dfc78e33.9b631","type":"inject","z":"2cabaefe.e05382","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"x":260,"y":560,"wires":[["24851e03.e8ac82"]]}]`

Node-RED version: v0.17.5 Node.js version: v8.9.3 Linux 4.9.59-v7+ arm LE

I also have this issue when using a DigiCert Certificate. Can anyone help? `docker run -v /home/ldap-admin/ldap/certificates:/container/service/slapd/assets/certs:rw -h ldap.xxx.de --name openldap -e LDAP_TLS_CRT_FILENAME=xxx.de.crt -e LDAP_TLS_KEY_FILENAME=xxx.de.key -e LDAP_TLS_DH_PARAM_FILENAME=xxx.de.pem -e LDAP_TLS_CA_CRT_FILENAME=xxx.de.ca.crt osixia/openldap...

Thanks for your findings, @johnthad. Any Idea how I can handle those files? JavaScripts File Object says, it is "image/tiff".