Can not loading adding integrations page. ELK v8.14.0 on Ubuntu

Elastic Stack Elasticsearch
1

Hi hero,

Please help a beginner.

Test environment
OS - Ubuntu 22.04.3 LTS
ELK version -
elasticsearch-8.14.0-linux-x86_64.tar
kibana-8.14.0-linux-x86_64.tar

I went through two situations.

  1. When I installed ELK at home, everything worked fine.
  2. When I installed ELK at work, I couldn't check the adding integrations page. It became infinite loading. The company does not have a policy to block access to the Internet.

My goal is to solve situation number 2.
The only thing I want is to see the adding integrations page in Elasticsearch.

The following is the log that appears when a problem occurs.
[ERROR][plugins.fleet] Failed to fetch latest version of synthetics from registry: Error connecting to package registry: request to https://epr.elastic.co/search?package=synthetics&prerelease=true&kibana.version=8.14.0 failed, reason: self-signed certificate in certificate chain

I did the same thing with the same file worked fine at home, but the problem only occurred at company and I realized it was a self-signed certificate issue.

I already tried to solve it through several ways, but it still didn't work out.
I am a beginner in Elastic.
I'd like to solve it as simply as possible.

Below is the full content of ELK yml file.
I changed the .(dot) to _ for posting purposes.

<elasticsearch.yml>
xpack.security.enabled: true
xpack.security.enrollment.enabled: true

xpack.security.http.ssl:
enabled: true
keystore.path: certs/http.p12

xpack.security.transport.ssl:
enabled: true
verification_mode: certificate
keystore.path: certs/transport.p12
truststore.path: certs/transport.p12

cluster.initial_master_nodes: ["ABCD-1234"]

http_host: 0_0_0_0

<kibana.yml>
elasticsearch.hosts: ['https://192_168_254_1:9200']
elasticsearch.serviceAccountToken: AAEAAWVsYXN0aWMva2liYW5hL2Vucm9sbC1wcm9jZXNzLXRva2VuLTE3MTgyNjY1Nzk3MDA6Y0xyT1FuZmlSeDI0aTV2N01nUzV6UQ
elasticsearch.ssl.certificateAuthorities: [/home/es/kibana-8.14.0/data/ca_1718266580760.crt]
xpack.fleet.outputs: [{id: fleet-default-output, name: default, is_default: true, is_default_monitoring: true, type: elasticsearch, hosts: ['https://192_168_254_1:9200'], ca_trusted_fingerprint: 45aec6230a34ea6fa052c4ef9ba4586171265753e858f9e7180ab930aab0c4dd}]

This is the connection address I use when connecting via ELK.
http://localhost:5601

I want to solve it in the simplest way possible, whether to use a certificate or not.

If you have more questions or more information, please let me know.
Thanks in advance.

Regards
-Ahn-

2

Hi @ahn,

Welcome! Is it Elasticsearch 8.14 that you've tried to instlal both at home and at work? Do you see any errors in the logs or the Chrome DevTools console?

3

I don't think there is any issue in any elastic tool, it seems an issue on the network you have at your company.

Your company may not be blocking access to the internet, but it may be using a proxy or doing ssl inspection.

You need to check it, I would say that probably there is something like SSL inspection being done.

4

Welcome! Is it Elasticsearch 8.14 that you've tried to instlal both at home and at work?

->
Yes, both 8.14

Do you see any errors in the logs or the Chrome DevTools console?

->
As in the text, this is the error log.
[ERROR][plugins.fleet] Failed to fetch latest version of synthetics from registry: Error connecting to package registry: request to https://epr.elastic.co/search?package=synthetics&prerelease=true&kibana.version=8.14.0 failed, reason: self-signed certificate in certificate chain

Thank you.

5

You're right. I think it's 100% a certificate issue. Is there any way I can solve this problem on my own?
Thank you.

6

How are you running Elasticsearch? Are you using Docker? You might need to specify the root certificate as discussed in this thread.

7

I don't think so, as mentioned it seems to be a network issue, so you need to check internally in your company who manages the network and ask for help to troubleshoot this issue.

8

Hi, leandrojmp
OK I will ask security manager.
Thank you very much.
Regards
-Ahn

9

Hi carly.richmond,
It's not Docker-based.
OK I will ask security manager.
Thank you very much.
Regards
-Ahn