546 Unknown Application / TLS Error

The HTTP 546 status code is an unofficial server error used by Akamai Enterprise Application Access (EAA) and Edgio with different meanings. Akamai EAA returns 546 Unknown Application when the Login/Authentication POP lacks the application configuration, while Edgio returns 546 TLS Error when TLS negotiation with the global POP fails.

Table of Contents

Usage specific to Akamai EAA

Akamai EAA routes Authentication requests through Login/Authentication POPs holding configuration data for each protected application. This configuration includes the application's access policies, IdP bindings, and connector assignments.

A 546 Unknown Application indicates the Login/Authentication POP does not have the application configuration. This typically occurs when a deployment has not yet propagated to the POP handling the request, or when the application was recently created and configuration distribution is still in progress.

Usage specific to Edgio

Edgio secures traffic between edge POPs and global POPs using TLS. The edge POP establishes a TLS connection to the global POP before forwarding the client request.

A 546 TLS Error indicates an error occurred during TLS negotiation between the edge POP and the global POP. Causes include certificate expiration within the Edgio infrastructure, TLS version mismatches, and transient handshake failures during platform updates.

SEO impact

Search engines treat 546 responses as server errors. Persistent errors cause crawlers to reduce crawl frequency and eventually drop affected URLs from the index.

Example

Akamai EAA

A user accesses an enterprise application through the Akamai EAA portal, but the Login/Authentication POP has not received the application configuration.

Request

GET /app/resource HTTP/1.1
Host: app.example.re
Accept: text/html

Response

HTTP/1.1 546 Unknown Application
Date: Mon, 02 Mar 2026 10:40:00 GMT
Content-Type: text/html
Server: AkamaiEAA

<html>
<head><title>546 Unknown Application</title></head>
<body>
<h1>546 Unknown Application</h1>
<p>Application configuration not found</p>
</body>
</html>

Edgio

A client request reaches the Edgio edge POP, but TLS negotiation with the global POP fails.

Request

GET /page HTTP/1.1
Host: cdn.example.re
Accept: text/html

Response

HTTP/1.1 546 Edgio Global POP TLS Error
Date: Mon, 02 Mar 2026 10:41:00 GMT
Content-Type: text/html
Server: ECAcc

<html>
<head>
  <title>546 Edgio Global POP TLS Error</title>
</head>
<body>
<h1>546 Edgio Global POP TLS Error</h1>
<p>TLS negotiation with global POP failed</p>
</body>
</html>

How to fix

Akamai EAA:

  • Verify the application is deployed and the deployment status shows as active in the Akamai EAA management console.
  • Wait for configuration propagation to complete if the application was recently created or modified. Propagation across all POPs takes several minutes.
  • Contact Akamai support to verify whether the application configuration has reached the specific Login/Authentication POP.

Edgio:

  • Check the Edgio status page for platform incidents affecting TLS connectivity between POPs.
  • Retry the request after a short delay. Transient TLS handshake failures during platform updates often resolve automatically.
  • If the error persists, contact Edgio support to investigate certificate or TLS configuration issues within the platform infrastructure.

Takeaway

The 546 status code is an unofficial server error with platform-specific meanings. Akamai EAA returns 546 Unknown Application when application configuration has not reached the POP, while Edgio returns 546 TLS Error when internal TLS negotiation fails between edge and global POPs.

See also

Last updated: March 6, 2026