I have encountered this problem: I need to send http request but there are self-signed certificate. If I would ignore SSL issues request returns html that telling me to download CA root certificate. Is it possible to add this root certificate to request? And if it is, then how?
I tried to add it into custom image and run it, but it didn’t changed anything.
##Error
SSL Issue: consider using the ‘Ignore SSL issues’ option
self-signed certificate in certificate chain
We don’t have an option to add a cert to a request that isn’t used for authentication but you could add the cert to the containers CA list which should work.
What I find really odd though is setting the ignore ssl issues option will work for the connection and I am not sure why you are seeing the html to download a certificate that is not a normal thing and makes me think either the url is wrong or the service you are connecting to needs certificate authentication.
Yeah, sure. I am trying to connect to sberbank.ru. Their security certificate was revoked due to sanctions so they moved to (national? i am not sure exactly).
below is json of workflow (there are not much, just http request): { "name": "My workflow 12", "nodes": [ { "parameters": {}, "id": "d4c0c7b1-b174-4aa3-9090-65465a78c988", "name": "When clicking \"Execute Workflow\"", "type": "n8n-nodes-base.manualTrigger", "typeVersion": 1, "position": [ 700, 400 ] }, { "parameters": { "url": "https://www.sberbank.ru/", "options": {} }, "id": "a4c89bea-0913-4697-b964-30d4051de16e", "name": "HTTP Request", "type": "n8n-nodes-base.httpRequest", "typeVersion": 4.1, "position": [ 920, 400 ] } ], "pinData": {}, "connections": { "When clicking \"Execute Workflow\"": { "main": [ [ { "node": "HTTP Request", "type": "main", "index": 0 } ] ] } }, "active": false, "settings": { "executionOrder": "v1" }, "versionId": "95a14ace-5e84-4ca3-9d50-fea1ceab0985", "id": "BMFrHXQQ02N0VVSL", "meta": { "instanceId": "4e68fdd7edde2844160870e34e2b7573b94eae13039038029c2d6760d9c43268" }, "tags": [] }
Also, thanks a lot after one more try, there are no more “self-signed certificate in certificate chain” error, but they are still returning that html, so probably the problem is on their part now.
It looks like the page you are accessing does just contain the certificate link on it, it looks like they require a user agent as well so if you add User-Agent as a header and set it to something like Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:127.0) Gecko/20100101 Firefox/127.0 it will get you one step further, The downside though is their site then shows a message to say they require javascript which means you might not be able to do anything with this site using the HTTP Request node unless they have a proper API.