# New insallation stuck at loading integrations

**URL:** <https://discuss.elastic.co/t/new-insallation-stuck-at-loading-integrations/370283>\
**Category:** Elastic Search\
**Created:** [November 10, 2024, 12:30pm UTC](https://discuss.elastic.co/t/new-insallation-stuck-at-loading-integrations/370283 "2024-11-10T12:30:57Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![ahsan0331](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@ahsan0331](https://discuss.elastic.co/u/ahsan0331)\
**Post date:** [November 10, 2024, 12:30pm UTC](https://discuss.elastic.co/t/new-insallation-stuck-at-loading-integrations/370283/1 "2024-11-10T12:30:57Z")

</div>

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](https://www.fosstechnix.com/how-to-install-elastic-stack-on-ubuntu-24-04/)**
>
> how to install the Elastic Stack on Ubuntu 24.04 LTS. The ELK Stack consists of Elasticsearch, Logstash, and Kibana, with Filebeat often used to ship logs to Logstash.

regards

 ![Screenshot 2024-11-10 175209](https://us1.discourse-cdn.com/elastic/original/3X/8/3/833fbdadb9f7a262fb94377f42e7650b03c152c5.png)

---

<div class="post-metadata">

**Author:** ![gpineda\_dev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gpineda_dev/32/137494_2.png) [@gpineda\_dev](https://discuss.elastic.co/u/gpineda_dev)\
**Post date:** [November 10, 2024, 1:09pm UTC](https://discuss.elastic.co/t/new-insallation-stuck-at-loading-integrations/370283/2 "2024-11-10T13:09:07Z")

</div>

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](https://www.elastic.co/guide/en/fleet/current/epr-proxy-setting.html)

---

<div class="post-metadata">

**Author:** ![ahsan0331](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@ahsan0331](https://discuss.elastic.co/u/ahsan0331)\
**Post date:** [November 10, 2024, 1:11pm UTC](https://discuss.elastic.co/t/new-insallation-stuck-at-loading-integrations/370283/3 "2024-11-10T13:11:54Z")

</div>

the machine has direct connection no proxy in between.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [November 10, 2024, 2:30pm UTC](https://discuss.elastic.co/t/new-insallation-stuck-at-loading-integrations/370283/4 "2024-11-10T14:30:34Z")

</div>

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](https://discuss.elastic.co/t/fleet-dashboard-not-loading-or-taking-too-long-to-load/366657/22):
>
> 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

---

<div class="post-metadata">

**Author:** ![ahsan0331](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@ahsan0331](https://discuss.elastic.co/u/ahsan0331)\
**Post date:** [November 10, 2024, 2:52pm UTC](https://discuss.elastic.co/t/new-insallation-stuck-at-loading-integrations/370283/5 "2024-11-10T14:52:02Z")

</div>

```auto
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:~$

```

```auto
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:~$

```

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [November 10, 2024, 2:57pm UTC](https://discuss.elastic.co/t/new-insallation-stuck-at-loading-integrations/370283/6 "2024-11-10T14:57:46Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ahsan0331](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@ahsan0331](https://discuss.elastic.co/u/ahsan0331)\
**Post date:** [November 10, 2024, 3:46pm UTC](https://discuss.elastic.co/t/new-insallation-stuck-at-loading-integrations/370283/7 "2024-11-10T15:46:01Z")

</div>

> [@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.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [November 10, 2024, 4:01pm UTC](https://discuss.elastic.co/t/new-insallation-stuck-at-loading-integrations/370283/8 "2024-11-10T16:01:11Z")

</div>

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](https://www.elastic.co/guide/en/elasticsearch/reference/current/deb.html)**

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

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

---

<div class="post-metadata">

**Author:** ![ahsan0331](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@ahsan0331](https://discuss.elastic.co/u/ahsan0331)\
**Post date:** [November 10, 2024, 5:07pm UTC](https://discuss.elastic.co/t/new-insallation-stuck-at-loading-integrations/370283/9 "2024-11-10T17:07:23Z")

</div>

> [@stephenb](#):
>
> basic setup (not recommended for

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

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 8, 2024, 5:07pm UTC](https://discuss.elastic.co/t/new-insallation-stuck-at-loading-integrations/370283/10 "2024-12-08T17:07:53Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.