New insallation stuck at loading integrations

[ahsan0331 (Ahsan)]

Hi
I am new to this world of elastic. looks really fantastic. i was about to explore it for netflow. i installed elk stack. and when i browse the page at

host:5601/app/integrations/browse

there only the loading circle rotates does nothing. i have installed it on test machine having 8 cores and 16gb ram and 500gb ssd.

i have tried rebooting it but still not doing anything. internet is working on the server.
Please if someone can guide me .

i followed this guide.

How to Install Elastic Stack on Ubuntu 24.04 LTS

regards

[gpineda_dev (Guillaume Pineda)]

Hi @ahsan0331, I experienced a similar issue running elk with docker-inside a company network when the HTTP_PROXY is not properly configured in the containers.

Have a look at : Set the proxy URL of the Elastic Package Registry | Fleet and Elastic Agent Guide [8.15] | Elastic

[ahsan0331 (Ahsan)]

the machine has direct connection no proxy in between.

[stephenb (Stephen Brown)]

Hi @ahsan0331

Welcome to the community, sorry you are having issues

Kibana connects with several services to be able to load that page we, sometimes corporate FWs can block

Take a look at this post

Fleet Dashboard Not Loading or Taking Too Long to Load

Hi @prabhuteja From inside your Kibana container did you try to make sure you have connectivity to the artifact and epr package repository Run these from inside your Kibana container. Show the commands and the outputs curl -v https://artifacts.elastic.co/downloads curl -v https://epr.elastic.co

And try the curls from the Kibana server / container

Please Show the command and result

[ahsan0331 (Ahsan)]

elasticflow@elastic:~$
elasticflow@elastic:~$ curl -v https://epr.elastic.co
* Host epr.elastic.co:443 was resolved.
* IPv6: 2600:1901:0:1d7::
* IPv4: 34.120.127.130
*   Trying 34.120.127.130:443...
* Connected to epr.elastic.co (34.120.127.130) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519 / RSASSA-PSS
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=elastic.co
*  start date: Sep 24 22:54:41 2024 GMT
*  expire date: Dec 23 22:54:40 2024 GMT
*  subjectAltName: host "epr.elastic.co" matched cert's "epr.elastic.co"
*  issuer: C=US; O=Let's Encrypt; CN=R11
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://epr.elastic.co/
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: epr.elastic.co]
* [HTTP/2] [1] [:path: /]
* [HTTP/2] [1] [user-agent: curl/8.5.0]
* [HTTP/2] [1] [accept: */*]
> GET / HTTP/2
> Host: epr.elastic.co
> User-Agent: curl/8.5.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/2 200
< content-length: 72
< strict-transport-security: max-age=31536000; includeSubDomains
< via: 1.1 google
< date: Sun, 10 Nov 2024 14:50:51 GMT
< content-type: application/json
< age: 162
< cache-control: max-age=10,public
< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
<
{
  "service.name": "package-registry",
  "service.version": "1.26.0"
}
* Connection #0 to host epr.elastic.co left intact
elasticflow@elastic:~$

elasticflow@elastic:~$
elasticflow@elastic:~$ curl -v https://epr.elastic.co
* Host epr.elastic.co:443 was resolved.
* IPv6: 2600:1901:0:1d7::
* IPv4: 34.120.127.130
*   Trying 34.120.127.130:443...
* Connected to epr.elastic.co (34.120.127.130) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519 / RSASSA-PSS
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=elastic.co
*  start date: Sep 24 22:54:41 2024 GMT
*  expire date: Dec 23 22:54:40 2024 GMT
*  subjectAltName: host "epr.elastic.co" matched cert's "epr.elastic.co"
*  issuer: C=US; O=Let's Encrypt; CN=R11
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://epr.elastic.co/
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: epr.elastic.co]
* [HTTP/2] [1] [:path: /]
* [HTTP/2] [1] [user-agent: curl/8.5.0]
* [HTTP/2] [1] [accept: */*]
> GET / HTTP/2
> Host: epr.elastic.co
> User-Agent: curl/8.5.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/2 200
< content-length: 72
< strict-transport-security: max-age=31536000; includeSubDomains
< via: 1.1 google
< date: Sun, 10 Nov 2024 14:53:33 GMT
< content-type: application/json
< age: 61
< cache-control: max-age=10,public
< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
<
{
  "service.name": "package-registry",
  "service.version": "1.26.0"
}
* Connection #0 to host epr.elastic.co left intact
elasticflow@elastic:~$

[stephenb (Stephen Brown)]

To confirm you ran this from the Kibana server correct? Not where you browser is.

The commands are a little off but the look to have made connection to the endpoints.

You will need to look at the Kibana logs and look for errors timeouts you may need To set the log level to debug.

Share any warn or errors.

[ahsan0331 (Ahsan)]

@stephenb

ran this from the Kibana server correct? Not where you browser is.

The commands are a little off but the look to have made connection to the endpoints.

You will need to

yes these were run directly on the server not browser.

[stephenb (Stephen Brown)]

Ohhh you followed not our official documentation...

And that directions disable security so none of the features you're trying will work.

From those instructions

For a basic setup (not recommended for production), disable security features.

You should follow our official documentation to install. I would uninstall and start from scratch.

Install Elasticsearch with Debian Package | Elasticsearch Guide [8.15] | Elastic

In order to use Fleet and integrations, security needs to be enabled

It's best to use our documentation, not third party

[ahsan0331 (Ahsan)]

@stephenb

basic setup (not recommended for

Thanks a lot for your response i will install using official documentation.