Fixing "ERR_SSL_PROTOCOL_ERROR" when opening the Astra dashboard or help center

Last updated: November 18, 2026

Applies to: the Astra dashboard and help center

What you're seeing

When you open the Astra dashboard or help center, your browser shows one of these errors instead of the page:

  • ERR_SSL_PROTOCOL_ERROR (Chrome, Edge)

  • "Secure Connection Failed" or SSL_ERROR_PROTOCOL_VERSION_ALERT (Firefox)

  • "Safari can't establish a secure connection" (Safari)

The error appears in every browser and on every device that uses the same network. A VPN doesn't change it, and DNS and port 443 look fine.

Why this happens

Astra only accepts secure connections that use TLS 1.3. Older versions (TLS 1.2 and below) are rejected during the handshake, before any page loads. That is why the browser shows a generic SSL error and not an Astra error page.

This usually means something on your network is negotiating an older TLS version on your behalf. The most common causes are:

  • A corporate proxy or firewall that inspects HTTPS traffic ("TLS inspection" or "SSL inspection") and only supports TLS 1.2.

  • An older security gateway, web filter or antivirus with HTTPS scanning.

  • A very old operating system, browser or device that doesn't support TLS 1.3.

The Astra platform itself is not affected. If you can open the dashboard from a different network, such as a mobile hotspot, the problem is on the first network.

How to fix it

Ask your IT or network team to do one of the following:

  1. Enable TLS 1.3 on the proxy, firewall or security gateway that your traffic goes through.

  2. Exempt *.getastra.com from TLS/SSL inspection, or add it to the allow list (bypass list) of your proxy or web filter.

  3. Update the client, if it is an old device or browser. Current versions of Chrome, Edge, Firefox and Safari all support TLS 1.3.

After the change, close and reopen the browser, then open the dashboard again.

How to confirm the cause

Run these two commands from an affected computer (macOS, Linux, or Windows 10/11 with curl installed):

curl -v https://my.getastra.com
curl -v --tls-max 1.2 https://my.getastra.com

Result

What it means

First command connects, second fails with a "protocol version" error

Expected. Astra requires TLS 1.3, and your network allows it. If the browser still fails, the cause is the browser or device.

First command also fails with a protocol or handshake error

Your network or device isn't allowing TLS 1.3. Use the fixes above.

First command works but the browser fails

Check the browser version, browser extensions, and any endpoint security software.

The second command is meant to fail. It forces the older TLS version to show that it is rejected.

Still stuck?

Contact Astra support and include:

  • The full output of both commands above

  • The exact error shown in the browser

  • Your public IP address (how to find and share your IP address)

  • The name of your proxy, firewall or web filter, if you know it

  • The time and date of an attempt (with your time zone)