You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unable to connect to Elasticsearch when self-signed certificate is used in ES. Response when testing credentials: "SELF_SIGNED_CERT_IN_CHAIN". Also HTTP request does not work, even no error message in response. "Ignore SSL issues" option is selected.
To Reproduce
Create Elasticsearch deployment with self-signed certificate (default certificate generated during Elasticsearch installation)
Note or re-generate password for 'elastic' built-in user
Use proper credentials when configuring Elasticsearch node
Test credentials
Couldn’t connect with these settings SELF_SIGNED_CERT_IN_CHAIN will be printed
Expected behavior
Even if Elasticsearch has self-signed certificate the communication with ES should be permitted from n8n.
Operating System
Ubuntu Linux 22.04
n8n Version
1.42.1
Node.js Version
18.20.3
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered:
Thanks for the report, It looks like while the credential test fails the node should still work. I have popped in a PR that fixes the issue with the credential test. Once reviewed it will be merged and available in a future release.
Bug Description
Unable to connect to Elasticsearch when self-signed certificate is used in ES. Response when testing credentials: "SELF_SIGNED_CERT_IN_CHAIN". Also HTTP request does not work, even no error message in response. "Ignore SSL issues" option is selected.
To Reproduce
Couldn’t connect with these settings SELF_SIGNED_CERT_IN_CHAIN
will be printedExpected behavior
Even if Elasticsearch has self-signed certificate the communication with ES should be permitted from n8n.
Operating System
Ubuntu Linux 22.04
n8n Version
1.42.1
Node.js Version
18.20.3
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: