# Upgrade to a Premium plan - Your connection is not private

**URL:** <https://forums.percona.com/t/upgrade-to-a-premium-plan-your-connection-is-not-private/24185>\
**Category:** Percona Monitoring and Management (PMM)\
**Created:** [August 3, 2023, 9:10pm UTC](https://forums.percona.com/t/upgrade-to-a-premium-plan-your-connection-is-not-private/24185 "2023-08-03T21:10:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Naresh9999](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/naresh9999/32/5568_2.png) [@Naresh9999](https://forums.percona.com/u/Naresh9999)\
**Post date:** [August 3, 2023, 9:10pm UTC](https://forums.percona.com/t/upgrade-to-a-premium-plan-your-connection-is-not-private/24185/1 "2023-08-03T21:10:52Z")

</div>

When I opened the below link, I got the below error.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/4/4f50b51ad18aa4ab41cedd382cc1737c04810e0a.png)

 ![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/e/e65b41808bedd15cf7c4cd34dbfc843593c44d08.png)

> **[Database Support You Can Count On](https://www.percona.com/services/support?utm_medium=banner&utm_campaign=advisors_getmore&utm_source=pmm-tid-33582bfec76b4bd9b53a5fd1528d7d7d)**
>
> Percona database support services ensures 24x7x365 database support for better performance. Highly responsive, effective and affordable.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/e/e0fa59dfa70ed540fc4846b840d39e0064db5968.png)

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [August 4, 2023, 3:53am UTC](https://forums.percona.com/t/upgrade-to-a-premium-plan-your-connection-is-not-private/24185/2 "2023-08-04T03:53:56Z")

</div>

Hello @Naresh9999,  
When I try I don’t get that. Are you using a proxy of some kind? The certificate is valid for me. Using curl on CLI it says the certificate is valid:

```auto
$ curl --verbose https://per.co.na/subscription2
* Trying 52.2.56.64:443...
* Connected to per.co.na (52.2.56.64) port 443 (#0)
* ALPN: offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-AES128-GCM-SHA256
* ALPN: server accepted h2
* Server certificate:
* subject: CN=per.co.na
* start date: May 11 00:00:00 2023 GMT
* expire date: Aug 9 23:59:59 2023 GMT
* issuer: C=AT; O=ZeroSSL; CN=ZeroSSL RSA Domain Secure Site CA
* SSL certificate verify ok.

```

---

<div class="post-metadata">

**Author:** ![Naresh9999](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/naresh9999/32/5568_2.png) [@Naresh9999](https://forums.percona.com/u/Naresh9999)\
**Post date:** [August 4, 2023, 7:16am UTC](https://forums.percona.com/t/upgrade-to-a-premium-plan-your-connection-is-not-private/24185/3 "2023-08-04T07:16:28Z")

</div>

@matthewb Thanks for the help. Usually [percona.com](http://percona.com) is allowed by default, but **per.co.na** is blocked in our organization. Now the security team has allowed it, and it’s working fine.