Hello,
I am using Elasticsearch and kibana 8.0.0, and it was working perfectly.
Today I run git pull and now kibana is not working anymore, when I try to run it, I am getting these errors:
(node:48280) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
Node.js process-warning detected:
DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
at Object.connect (_tls_wrap.js:1621:15)
at HttpsAgent.createConnection (https.js:132:22)
at HttpsAgent.createSocket (/home/ELK-8_0_0/kibana/node_modules/agentkeepalive/lib/_http_agent.js:265:26)
at HttpsAgent.createSocket (/home//ELK-8_0_0/kibana/node_modules/agentkeepalive/lib/agent.js:77:11)
at HttpsAgent.addRequest (/home//ELK-8_0_0/kibana/node_modules/agentkeepalive/lib/_http_agent.js:239:10)
at new ClientRequest (_http_client.js:298:16)
at Object.request (https.js:316:10)
at Object.request (/home/ELK-8_0_0/kibana/node_modules/agent-base/patch-core.js:25:22)
at HttpConnector.request (/home/ELK-8_0_0/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:182:23)
at sendReqWithConnection (/home/ELK-8_0_0/kibana/node_modules/elasticsearch/src/lib/transport.js:263:35)
at Object.utils.applyArgs (/home/ELK-8_0_0/kibana/node_modules/elasticsearch/src/lib/utils.js:188:19)
at wrapper (/home/ELK-8_0_0/kibana/node_modules/lodash/lodash.js:5213:19)
at processTicksAndRejections (internal/process/task_queues.js:79:11)
at runNextTicks (internal/process/task_queues.js:66:3)
at processTimers (internal/timers.js:494:9)
Terminating process...
server crashed with status code 1
my config in kibana.yml:
server.port: 5601
server.host: "X.X.X.X"
server.name: "Kibana"
elasticsearch.hosts: ["https://X.X.X.X:9200"]
elasticsearch.username: "kibana_system"
elasticsearch.password: "password"
server.ssl.enabled: true
server.ssl.certificate: "KIBANA.crt"
server.ssl.key: "KIBANA.key"
elasticsearch.ssl.certificateAuthorities: [ "elasticsearch-ca.pem" ]
elasticsearch.ssl.verificationMode: full
Thanks for your help.
Can you try pulling again? It looks like lodash isn't handling that new Node 12 deprecation warning properly.
I just tried again, and I still have the same issue 
the output of the command yarn kbn bootstrap :
yarn run v1.22.5
$ node scripts/kbn bootstrap
info [kibana] running yarn
$ node ./preinstall_check
[1/5] Validating package.json...
[2/5] Resolving packages...
warning Resolution field "trim@0.0.3" is incompatible with requested version "trim@0.0.1"
warning Resolution field "trim@0.0.3" is incompatible with requested version "trim@0.0.1"
warning Resolution field "@types/node@12.19.4" is incompatible with requested version "@types/node@8.10.54"
warning Resolution field "typescript@4.1.2" is incompatible with requested version "typescript@~3.7.2"
warning Resolution field "prismjs@1.22.0" is incompatible with requested version "prismjs@~1.16.0"
warning Resolution field "typescript@4.1.2" is incompatible with requested version "typescript@^3.2.2"
warning Resolution field "schema-utils@1.0.0" is incompatible with requested version "schema-utils@^0.3.0"
warning Resolution field "trim@0.0.3" is incompatible with requested version "trim@0.0.1"
warning Resolution field "typescript@4.1.2" is incompatible with requested version "typescript@^3.0.3"
warning Resolution field "typescript@4.1.2" is incompatible with requested version "typescript@^3.4.5"
warning Resolution field "trim@0.0.3" is incompatible with requested version "trim@0.0.1"
warning Resolution field "typescript@4.1.2" is incompatible with requested version "typescript@^3.3.3333"
success Already up-to-date.
succ yarn.lock analysis completed without any issues
succ 25 bootstrap builds are cached
info [x-pack] running [kbn:bootstrap] script
succ [x-pack] bootstrap complete
info [kibana] running [kbn:bootstrap] script
succ [kibana] bootstrap complete
Done in 10.82s.
and the output of the command yarn start --run-examples still output the same errors that I have shared.
Our team is investigating right now. As a potential workaround this could work:
NODE_OPTIONS="--no-warnings" yarn start --run-examples
or if you run it directly:
node --no-warnings scripts/kibana --run-examples
Thanks @Marius_Dragomir , the first command worked for me
Please keep me updated once the problem is solved to pull again
Best regards.