# Getting 403 code while connecting to elastic

**URL:** <https://discuss.elastic.co/t/getting-403-code-while-connecting-to-elastic/325615>\
**Category:** Kibana\
**Created:** [February 15, 2023, 12:58pm UTC](https://discuss.elastic.co/t/getting-403-code-while-connecting-to-elastic/325615 "2023-02-15T12:58:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![fvtarnovskiy](https://avatars.discourse-cdn.com/v4/letter/f/bc79bd/32.png) [@fvtarnovskiy](https://discuss.elastic.co/u/fvtarnovskiy)\
**Post date:** [February 15, 2023, 12:58pm UTC](https://discuss.elastic.co/t/getting-403-code-while-connecting-to-elastic/325615/1 "2023-02-15T12:58:25Z")

</div>

Hello!

We are a cloud provider from Uzbekistan pro-data.tech ([https://pro-data.tech/](https://pro-data.tech/)).  
Please help in solving the problem - when trying to access Elastic, we get an error code 403 from all our addresses (95.47.127.0/24).

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/6/f62b273ed747828e9f8100e1b4b0bf3e6f5e1592.png)

curl -vvl "[https://epr.elastic.co/search?package=system&internal=true&kibana.version=7.16.1](https://epr.elastic.co/search?package=system&internal=true&kibana.version=7.16.1)"

- Trying 34.120.127.130:443...
- Connected to [epr.elastic.co](http://epr.elastic.co/) (34.120.127.130) port 443 (#0)
- ALPN, offering h2
- ALPN, offering http/1.1
- CAfile: /etc/ssl/certs/ca-certificates.crt
- CApath: /etc/ssl/certs
- TLSv1.0 (OUT), TLS header, Certificate Status (22):
- TLSv1.3 (OUT), TLS handshake, Client hello (1):
- TLSv1.2 (IN), TLS header, Certificate Status (22):
- TLSv1.3 (IN), TLS handshake, Server hello (2):
- TLSv1.2 (IN), TLS header, Finished (20):
- TLSv1.2 (IN), TLS header, Supplemental data (23):
- 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.2 (OUT), TLS header, Finished (20):
- TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
- TLSv1.2 (OUT), TLS header, Supplemental data (23):
- TLSv1.3 (OUT), TLS handshake, Finished (20):
- SSL connection using TLSv1.3 / TLS\_AES\_256\_GCM\_SHA384
- ALPN, server accepted to use h2
- Server certificate:
- subject: [CN=appsearch.elastic.co](http://cn%3Dappsearch.elastic.co/)
- start date: Jan 8 23:21:29 2023 GMT
- expire date: Apr 9 00:14:40 2023 GMT
- subjectAltName: host "[epr.elastic.co](http://epr.elastic.co/)" matched cert's "[epr.elastic.co](http://epr.elastic.co/)"
- issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1D4
- SSL certificate verify ok.
- Using HTTP2, server supports multiplexing
- Connection state changed (HTTP/2 confirmed)
- Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
- TLSv1.2 (OUT), TLS header, Supplemental data (23):
- TLSv1.2 (OUT), TLS header, Supplemental data (23):
- TLSv1.2 (OUT), TLS header, Supplemental data (23):
- Using Stream ID: 1 (easy handle 0x5627ef747550)
- TLSv1.2 (OUT), TLS header, Supplemental data (23):

> GET /search?package=system&internal=true&kibana.version=7.16.1 HTTP/2  
> Host: [epr.elastic.co](http://epr.elastic.co/)  
> user-agent: curl/7.81.0  
> accept: _/_

- TLSv1.2 (IN), TLS header, Supplemental data (23):
- TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
- TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
- old SSL session ID is stale, removing
- TLSv1.2 (IN), TLS header, Supplemental data (23):
- TLSv1.2 (OUT), TLS header, Supplemental data (23):
- TLSv1.2 (IN), TLS header, Supplemental data (23):
- TLSv1.2 (IN), TLS header, Supplemental data (23):  
\< HTTP/2 403  
\< content-length: 134  
\< content-type: text/html; charset=UTF-8  
\< date: Tue, 14 Feb 2023 11:54:07 GMT  
\< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000  
\<
- TLSv1.2 (IN), TLS header, Supplemental data (23):
- TLSv1.2 (IN), TLS header, Supplemental data (23):
- Connection #0 to host [epr.elastic.co](http://epr.elastic.co/) left intact  
\<!doctype html\>403403 Forbiddenro

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 15, 2023, 9:32pm UTC](https://discuss.elastic.co/t/getting-403-code-while-connecting-to-elastic/325615/2 "2023-02-15T21:32:05Z")

</div>

Please see [Are you getting 403's when downloading? Please read here first](https://discuss.elastic.co/t/are-you-getting-403s-when-downloading-please-read-here-first/307340/)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 15, 2023, 9:32pm UTC](https://discuss.elastic.co/t/getting-403-code-while-connecting-to-elastic/325615/3 "2023-02-15T21:32:08Z")

</div>