Error codes
This is the list of error codes returned by Get Error Statistics or Translate Error String tools together with short descriptions.
| Error code | Reason |
|---|---|
ERR_ACCESS_DENIED, 18.x.x.x | The client server was not authorized to access requested object or the origin server. |
ERR_ACCESS_DENIED|*, 18.1x.x.x | A string after the bar character that is not listed here likely means that the denial was based on auth:acl.deny metadata. The string is the first position in the deny list that caused the denial. |
ERR_ACCESS_DENIED | bad_cn_match, 18.2x.x.x | The CN on the certificate didn't match the host header. |
ERR_ACCESS_DENIED|bad_update_url, 18.3x.x.x | The request from mupdater contained invalid characters. |
ERR_ACCESS_DENIED|BotMan_Internal, 18.33x.x.x, 18.dx.x.x | Request was considered as Bot Manager Internal Request and denied potentially due to security config misconfiguration. |
ERR_ACCESS_DENIED|china_cdn, 18.32x.x.x | Request was denied because it was going to a ChinaCDN machine from outside China. |
ERR_ACCESS_DENIED|connect_loop, 18.4x.x.x | The CONNECT method detected a loop. |
ERR_ACCESS_DENIED|es_loading, 18.5x.x.x | The edge server received an updated edgescape database that is still loading. |
ERR_ACCESS_DENIED|ff_v1arl_nomdt, 18.6x.x.x | The unsupported version 1 of the ARL detected. |
ERR_ACCESS_DENIED|fp_auth_failed, 18.7x.x.x | Fingerprint authentication failed. |
ERR_ACCESS_DENIED|fwd_acl, 18.8x.x.x | Connection to forward host is not allowed because the host is not added in the Allowed Origins. |
ERR_ACCESS_DENIED|fwd_acl_ssl, 18.9x.x.x | Connection to forward host is not allowed because the host is not added in the Allowed Origins. |
ERR_ACCESS_DENIED|ipa_amplification, 18.10x.x.x | A client request was received with the internal edge server header. |
ERR_ACCESS_DENIED|ipv6-client, 18.11x.x.x | Internal error. For more details, contact the support team. |
ERR_ACCESS_DENIED|legacy_acl, 18.12x.x.x | Connection to forward host is not allowed because the host is not added in the Allowed Origins. |
ERR_ACCESS_DENIED|loop_*, 18.13.x.x.x | Loop detected. |
ERR_ACCESS_DENIED|mdt, 18.14x.x.x | Access is denied for this transaction per the metadata configuration. |
ERR_ACCESS_DENIED|mdt_update_failed, 18.15x.x.x | Mupdater request failed. |
ERR_ACCESS_DENIED|post_not_allowed, 18.16x.x.x | POST requests are blocked in the metadata configuration. |
ERR_ACCESS_DENIED|prefetch_push, 18.17x.x.x | The edge server received a PREFETCH_PUSH request from a peer, but this type of request was blocked in the metadata configuration. |
ERR_ACCESS_DENIED|ptk_default-deny-reason, 18.18x.x.x | The request was blocked by the Client IP. Check Allowed and Blocked lists in the configuration. |
ERR_ACCESS_DENIED|purge_*, 18.19x.x.x | Purge failed. |
ERR_ACCESS_DENIED|purge_ipcache_*, 18.20x.x.x | IP cache purge failed. |
ERR_ACCESS_DENIED|reqmod_*, 18.21x.x.x | Request-mod failed. |
ERR_ACCESS_DENIED|reqsat, 18.22x.x.x | Request-sat failed. |
ERR_ACCESS_DENIED|respmod, 18.23x.x.x | Response-mod failed. |
ERR_ACCESS_DENIED|rqacCustom, 0.x.x.x | The request was denied by a Web Application Firewall or Bot Manager rule configured. The rule is set to use a custom deny page. |
ERR_ACCESS_DENIED|Sec_Serve_Alternate | The request was denied by the configured Bot Manager rules. |
ERR_ACCESS_DENIED|ssl_port_acl, 18.24x.x.x | Server refused to go forward to a non-standard origin port. |
ERR_ACCESS_DENIED|store_rebuilding, 18.25x.x.x | Mupdater request was denied because the store is rebuilding. |
ERR_ACCESS_DENIED|streamauth*, 18.26x.x.x | Streamauth was not allowed or failed. |
ERR_ACCESS_DENIED|vr, 18.27x.x.x | The request was denied due to limits placed in the configuration for blocking requests when the overall traffic goes higher than the configured threshold. |
ERR_ACCESS_DENIED|waf, 18.28x.x.x | The request was denied by the configured Web Application Firewall rules. |
ERR_ADOBE_ERROR, 195.x.x.x | Internal error. For more details, contact the support team. |
ERR_AUTH_BROWSER_TOKEN_FAILED, 199.x.x.x | Internal error. For more details, contact the support team. |
ERR_BAD_CHUNKED_ENC, 122.x.x.x | The origin received bad chunked encoding. |
ERR_BAD_DEBUG_COOKIE, 17.x.x.x | Internal error. For more details, contact the support team. |
ERR_BAD_SWAPFILE_APPEND, 210.x.x.x | Internal error. For more details, contact the support team. |
ERR_BROTLI, 232.x.x.x | Internal error. For more details, contact the support team. |
ERR_CACHE_ACCESS_DENIED, 19.x.x.x | Internal error. For more details, contact the support team. |
ERR_CACHE_MGR_ACCESS_DENIED, 20.x.x.x | Internal error. For more details, contact the support team. |
ERR_CANNOT_FORWARD, 12.x.x.x | Internal error. For more details, contact the support team. |
ERR_CHUNK_INCOMPLETE, 178.x.x.x | The origin didn't send the last chunk of a file using Transfer-Encoding and the connection timed out. The edge server assumes that it has received the complete file, but treats it as uncacheable and logs the error. This behavior is controlled by the metadata. |
ERR_CLIENT_ABORT, 27.x.x.x | The request was not sent to the origin server. This is normal in the case of SureRoute test objects, when some requests are interrupted by the edge server if the fastest path to the origin has already been determined. |
ERR_CLIENT_ABORT_SLOW_DNS, 41.x.x.x | Internal error. For more details, contact the support team. |
ERR_CLIENT_CONTENT_MD5, 127.x.x.x | Internal error. For more details, contact the support team. |
ERR_CLIENT_READ_TIMEOUT, 95.x.x.x | The edge server timed out waiting for data from the client. This is more likely to be seen on POST requests. |
ERR_COMBINED_STORE, 230.x.x.x | Internal error. For more details, contact the support team. |
ERR_CONNECT_FAIL, 6.x.x.x | Connection to the origin server from the edge server timed out. The connection was never established. |
ERR_CONNECT_TIMEOUT, 97.x.x.x | Connection to the origin server from the edge server timed out. The connection was never established. |
ERR_CONTENT_POLICY, 218.x.x.x | Internal error. For more details, contact the support team. |
ERR_DANGEROUS_PORT, 44.x.x.x | The edge server couldn't go forward to requested port because it's in the deny-port list. |
ERR_DCA_BAD_ECFILE_REQ, 161.x.x.x | Internal error. For more details, contact the support team. |
ERR_DCA_BAD_WAR_REQ, 34.x.x.x | Internal error. For more details, contact the support team. |
ERR_DCA_CONTAINER, 37.x.x.x | Internal error. For more details, contact the support team. |
ERR_DCA_MAX_ESI_INCLUDE_SIZE, 36.x.x.x | Internal error. For more details, contact the support team. |
ERR_DCA_MAX_POST_SIZE, 33.x.x.x | Internal error. For more details, contact the support team. |
ERR_DCA_MAX_WAR_SIZE, 35.x.x.x | Internal error. For more details, contact the support team. |
ERR_DCV, 249.x.x.x | Fast Domain Control Validation encountered an error during the communication with DcvManager. |
ERR_DELEGATOR, 222.x.x.x | Internal error. For more details, contact the support team. |
ERR_DEVPOPS, 247.x.x.x | Internal error. For more details, contact the support team. |
ERR_DNS_FAIL, 11.x.x.x | The origin server IP address couldn't be resolved from the origin hostname. |
ERR_DNS_IN_REGION, 101.x.x.x | This is not an error and doesn’t indicate any failure in transaction. This means that an edge server contacted a different server in the same location. When this condition occurs, the edge server simply goes to the origin server to retrieve the content. |
ERR_DNS_TIMEOUT, 99.x.x.x | DNS lookup timeout. |
ERR_DRM_ACCESS_DENIED, 164.x.x.x | Internal error. For more details, contact the support team. |
ERR_ENCRYPT, 202.x.x.x | Internal error. For more details, contact the support team. |
ERR_EPD_ACCESS_DENIED, 219.x.x.x | The request was denied due to the Enhanced Proxy Detection feature. The error should include a description explaining the reason of the denial. |
ERR_ESI_BUF_ABORT, 108.x.x.x | ASI buffer copy operation was interrupted, most likely due to the client action. |
ERR_ESI_RESP, 109.x.x.x | Internal error. For more details, contact the support team. |
ERR_FIRST_BYTE_TIMEOUT, 221.x.x.x | Connection to the forward server timed out. |
ERR_FLV_SEEK, 177.x.x.x | Internal error. For more details, contact the support team. |
ERR_FORWARDING_DENIED, 13.x.x.x | The request was not sent to the origin server. This is normal in the case of SureRoute test objects, when some requests are interrupted by the edge server if the fastest path to the origin has already been determined. |
ERR_FP_MISMATCH, 111.x.x.x | Read error happened due to fingerprint mismatch. |
ERR_FRP_DENIED, 236.x.x.x | The forward robustness protection feature is active and it denies a forward request. |
ERR_FWD_BAD_HEADERS, 186.x.x.x | InvalidForwardReply: The response headers from the origin or the edge server parent were malformed or too large. The error occurs when the HTTP response status line is missing or malformed or when the origin or parent response headers exceed the size limit. This can often occur if Pragma: akamai-x-get-extracted-values was specified in the request to perform debugging, and there are a large number of X-Session-Info response headers. |
ERR_FWD_CAE_HEADERS, 203.x.x.x | This error indicates that the response headers from CAE failed the verification and forward request were treated as failed. |
ERR_FWD_CERT_INACTIVE, 55.x.x.x | The certificate's auth.ssl-fwd-certs.status flag was off. Edge servers with no specified client certificate when it's about to go forward, reject the request with a 403 HTTP status code and log one of the following error: ERR_FWD_CERT_SPEC_MISSING, ERR_FWD_CERT_MISSING, ERR_FWD_CERT_INACTIVE, or ERR_FWD_CERT_INVALID. |
ERR_FWD_CERT_INVALID, 56.x.x.x | Strict certificate checking was on and the certificate was invalid.Edge servers with no specified client certificate when it's about to go forward, reject the request with a 403 HTTP status code and log one of the following error: ERR_FWD_CERT_SPEC_MISSING, ERR_FWD_CERT_MISSING, ERR_FWD_CERT_INACTIVE, or ERR_FWD_CERT_INVALID. |
ERR_FWD_CERT_MISSING, 54.x.x.x | The certificate has not yet been loaded. Edge servers with no specified client certificate when it's about to go forward, reject the request with a 403 HTTP status code and log one of the following error: ERR_FWD_CERT_SPEC_MISSING, ERR_FWD_CERT_MISSING, ERR_FWD_CERT_INACTIVE, or ERR_FWD_CERT_INVALID. |
ERR_FWD_CONTENT_MD5, 126.x.x.x | Internal error. For more details, contact the support team. |
ERR_FWD_CONTENT_SHA256, 250.x.x.x | Internal error. For more details, contact the support team. |
ERR_FWD_ENTRY_ABORTED, 94.x.x.x | The forward connection to the origin from the edge server was interrupted. |
ERR_FWD_HASHED_SERIAL_NO_BACKEND_IP, 96.x.x.x | Y-map constructed with hashed serial didn't yield a backend IP in the response when resolved. The response is usually a VIP. The edge server forwards the request normally either to a cache parent or the origin. |
ERR_FWD_PCONN_SEC_DOWNGRADE, 39.x.x.x | The PConn is HTTP but the client expects HTTPS. Check if the metadata is not misconfigured. For example, the port doesn't match the protocol being used. |
ERR_FWD_PCONN_SEC_UPGRADE, 38.x.x.x | The PConn is HTTPS but the client expects HTTP. Check if the metadata is not misconfigured. For example, the port doesn't match the protocol being used. |
ERR_FWD_RATE_LIMIT_HOST_HASH_FULL, 48.x.x.x | The forward request couldn't be handled because the host hash was full and other hosts were handling their requests. |
ERR_FWD_RATE_LIMIT_NO_FREE_IPS, 49.x.x.x | Forward Rate Limiting failed for this request with an unspecified reason. This error excludes the following cases: - This request exceeded its allowed wait time in the queue set by fwd-rate-limit-queue-max-wait-ms. - The request was evicted from the forward queue because the queue had reached its limit and a request with higher priority or earlier request-header parse time took its spot. - The request couldn't be added to the forward queue because it was full. - The request couldn't be handled because the host hash was full and other hosts were handling their requests. |
ERR_FWD_RATE_LIMIT_Q_FILLED_UP, 46.x.x.x | The forward request was evicted from the forward queue. The queue had reached its limit and a request with higher priority or earlier request-header parse time took its spot. |
ERR_FWD_RATE_LIMIT_Q_FULL, 47.x.x.x | The forward request couldn't be added to the forward queue because it was full. |
ERR_FWD_RATE_LIMIT_Q_TIMEOUT, 45.x.x.x | This request exceeded its allowed wait time in the queue set by fwd-rate-limit-queue-max-wait-ms. |
ERR_FWD_RESIGNED_CERT, 175.x.x.x | A copy or signing operation failed when trying to resign the client certificate for transfer to the origin. |
ERR_FWD_SAME_REGION,43.x.x.x | The edge server attempted to contact its own region as the cache-h parent. After this error, it will attempt the next forward server, usually the origin. |
ERR_FWD_SSL_BAD_CERT, 31.x.x.x | Internal error. For more details, contact the support team. |
ERR_FWD_SSL_BAD_MDT_CIPHERS, 42.x.x.x | The ssl:security.ssl.forward-ciphers is not configured correctly. |
ERR_FWD_SSL_HANDSHAKE, 30.x.x.x | Internal error. For more details, contact the support team. |
ERR_FWD_SSL_OUT_OF_HANDSHAKES, 29.x.x.x | Internal error. For more details, contact the support team. |
ERR_FWD_STORAGE_BAD_RESPONSE, 214.x.x.x | Internal error. For more details, contact the support team. |
ERR_GETZIP_PROTOCOL_ERROR, 212.x.x.x | Internal error. For more details, contact the support team. |
ERR_GHOSTMON_CHK_MSG, 40.x.x.x | This request was a liveness check request generated by an edge server. |
ERR_GM_SUPPRESSED_ERR, 124.x.x.x | Internal error. For more details, contact the support team. |
ERR_GRID_INTEG_POC_NOT_MULTIPLE, 244.x.x.x | Internal error. For more details, contact the support team. |
ERR_GRID_INTEG_POC_SMALL_FRAG, 245.x.x.x | Internal error. For more details, contact the support team. |
ERR_GRID_INTEGRITY_CREATE_OBJECT, 242.x.x.x | Internal error. For more details, contact the support team. |
ERR_GZIP, 112.x.x.x | Read error happened due to compression. |
ERR_HRS_BARE_CRS_IN_HDR, 168.x.x.x | Possible request smuggling detected. There was a bare carriage returned and space within the headers. |
ERR_HRS_DUP_CONTENT_LEN, 169.x.x.x | Possible request smuggling detected. There was a second content-length header in the request. |
ERR_HRS_EMPTY_CONTINUATION, 167.x.x.x | Possible request smuggling detected. The header ended in CR/LF and the following line contained only spaces. |
ERR_HRS_FOLDED_LINE_ABORT, 254.x.x.x | Request interrupted due to folded line detection in header. |
ERR_HRS_HOST_HEADER_MISMATCH, 231.x.x.x | Possible request smuggling detected. There were multiple mismatching host headers or a mismatch between the host in the URI and a host header in the request. |
ERR_HRS_SPACE_AT_HDR_NAME_START, 251.x.x.x | Possible request smuggling detected. There is a space at the start of header name of a request. |
ERR_HRS_SPACE_IN_HDR_NAME, 166.x.x.x | Possible request smuggling detected. There was a space in the name of a request header. |
ERR_HRS_STRICT_MODE_HTTP_HDR_PARSING, 252.x.x.x | Request interrupted due to violating the strict mode in HTTP header parsing. |
ERR_HRS_UNAMBIGUOUS_MODE_HTTP_HDR_PARSING, 253.x.x.x | Request interrupted due to violating unambiguous mode in HTTP header parsing. |
ERR_HT_FAIL, 215.x.x.x | Internal error. For more details, contact the support team. |
ERR_HTTP_CONNECT_FAIL, 103.x.x.x | The HTTP connect failed. |
ERR_HTTP2_ERROR, 226.x.x.x | Internal error. For more details, contact the support team. |
ERR_ICP_DEADLOCK_DETECT, 180.x.x.x | The request was from another in-region edge server and the current edge server has a pending forward request to that edge server for the same object. This request is rejected since it may result in a deadlock. |
ERR_INVALID_CLIENT_CERT, 52.x.x.x | Internal error. For more details, contact the support team. |
ERR_INVALID_REQ, 227.x.x.x | The request's URL is not RFC compliant or there could be invalid HTTP headers in the request that cause it to be rejected. If this request uses DRM, check the token. |
ERR_INVALID_REQ_NOORIGINMDT | Internal error. For more details, contact the support team. |
ERR_INVALID_URL, 9.x.x.x | Internal error. For more details, contact the support team. |
ERR_IPTV_BAD_REQUEST, 193.x.x.x | Internal error. For more details, contact the support team. |
ERR_IPTV_NOT_FOUND, 194.x.x.x | Internal error. For more details, contact the support team. |
ERR_IPV6_SERVICE_UNAVAILABLE, 198.x.x.x | Internal error. For more details, contact the support team. |
ERR_LIFETIME_EXP, 2.x.x.x | The request's lifetime was exceeded. |
ERR_MANIFEST_MANIPULATION, 234.x.x.x | Internal error. For more details, contact the support team. |
ERR_MANIFEST_MANIPULATION_MASTER_NO_STREAM, 248.x.x.x | Internal error. For more details, contact the support team. |
ERR_METADATA_APPLY_FAILURE, 174.x.x.x | Internal error. For more details, contact the support team. |
ERR_MID_HEADER_ABORT, 237.x.x.x | Internal error. For more details, contact the support team. |
ERR_ERR_NETP, 233.x.x.x | Internal error. For more details, contact the support team. |
ERR_MP4_SEEK, 187.x.x.x | Internal error. For more details, contact the support team. |
ERR_NO_CLIENT_CERT, 51.x.x.x | Internal error. For more details, contact the support team. |
ERR_NO_FWD_HOSTS, 119.x.x.x | The edge server was unable to resolve any of the potential forward hostnames (origin or cache hierarchy parent or SureRoute parent) to an IP address. This indicates either a DNS problem or a problem with the map names being misconfigured or nonexistent. |
ERR_NO_GOOD_FWD_IP, 102.x.x.x | This is triggered by the Origin Health Detect feature. This code means that edge server intentionally didn't go forward to the origin because the origin is flagged as bad due to too many failures in retrieving content from it. This feature reduces the load on origin and gives some time for the origin to recover. As the origin starts to recover and get healthy, these errors go away. |
ERR_NO_ORIGIN_CLIENT_AUTH, 32.x.x.x | The server didn't request a certificate which is opposite to what was set in the metadata. |
ERR_NO_RELAY, 14.x.x.x | Internal error. For more details, contact the support team. |
ERR_NO_STICKY_PCONN, 179.x.x.x | Internal error. For more details, contact the support team. |
ERR_OBJ_OUT_OF_DATE, 121.x.x.x | The response object from origin is out of date. |
ERR_OBJ_TOO_BIG, 172.x.x.x | The response object is larger than what is permitted by the configuration settings. |
ERR_OCSP, 162.x.x.x | BD |
ERR_OCSP_BAD_BASICRESP, 59.x.x.x | The 'basicResponse' within the OCSP response was either not id-pkix-ocsp-basic or it could not be parsed. |
ERR_OCSP_BAD_NONCE, 67.x.x.x | The edge server sent a nonce to the responder but the responder sent a different nonce. |
ERR_OCSP_BAD_RESP, 58.x.x.x | Parsing of the DER encoded response failed. |
ERR_OCSP_CERT_REVOKED_AFFILIATIONCHANGED, 75.x.x.x | The certificate was revoked and the responder returned the affilicationChanged reason code. |
ERR_OCSP_CERT_REVOKED_CACOMPROMISE, 74.x.x.x | The certificate was revoked and the responder returned the caCompromise reason code. |
ERR_OCSP_CERT_REVOKED_CERTIFICATEHOLD, 78.x.x.x | The certificate was revoked and the responder returned the certifciateHold reason code. |
ERR_OCSP_CERT_REVOKED_CESSATIONOFOPERATION, 77.x.x.x | The certificate was revoked and the responder returned the cessationOfOperation reason code. |
ERR_OCSP_CERT_REVOKED_KEYCOMPROMISE, 73.x.x.x | The certificate was revoked and the responder returned the keyCompromise reason code. |
ERR_OCSP_CERT_REVOKED_NOSTATUS, 71.x.x.x | The certificate was revoked and the responder didn't specify why. |
ERR_OCSP_CERT_REVOKED_REMOVEFROMCRL, 79.x.x.x | The certificate was revoked and the responder returned the removeFromCrl reason code. |
ERR_OCSP_CERT_REVOKED_STATUS_UNRECOGN, 80.x.x.x | The certificate was revoked and the edge server didn't recognize the returned reason code. |
ERR_OCSP_CERT_REVOKED_SUPERSEDED, 76.x.x.x | The certificate was revoked and the responder returned the superseded reason code. |
ERR_OCSP_CERT_REVOKED_UNSPECIFIED, 72.x.x.x | The certificate was revoked and the responder specifically stated the reason to be unspecified. |
ERR_OCSP_CERT_STATUS_UNRECOGN, 82.x.x.x | The edge server didn't recognize the certificate status given by the responder. The edge server considers the certificate invalid. |
ERR_OCSP_CERT_UNKNOWN, 81.x.x.x | The OCSP responder didn't recognize the user's certificate. The edge server considers the certificate invalid. |
ERR_OCSP_CERTID_BAD_ALGO_IN_RESP, 238.x.x.x | Internal error. For more details, contact the support team. |
ERR_OCSP_CERTID_NOT_IN_RESP1, 69.x.x.x | One of the certificate IDs that was in edge server's request was not in the OCSP response. |
ERR_OCSP_CERTID_NOT_IN_RESP2, 70.x.x.x | One of the certificate IDs that was in edge server's request was not in the OCSP response. |
ERR_OCSP_INTERNAL, 91.x.x.x | An internal error occurred in the edge server while validating the response. Check cache.log for details. |
ERR_OCSP_NEXT_UPD_INVALID, 87.x.x.x | The next-update field could not be parsed. |
ERR_OCSP_NEXT_UPD_TOO_AHEAD, 89.x.x.x | The next-update field was way passed the current time based on the security.essl.slot-assignment.client-cert. ocsp.responder.next-upd-allowed-future-diff setting. |
ERR_OCSP_NEXT_UPD_TOO_OLD, 88.x.x.x | The next-update field was too old based on the security.essl.slot-assignment.client-cert. ocsp.responder.next-upd-allowed-future-diff setting. |
ERR_OCSP_NO_NONCE, 66.x.x.x | The edge server sent a nonce to the responder but the responder didn't send a nonce. |
ERR_OCSP_NOT_DONE, 92.x.x.x | OCSP processing failed. Check cache.log for details. |
ERR_OCSP_NOT_HTTP_OK, 57.x.x.x | The HTTP response code was not 200 OK. |
ERR_OCSP_STAT_INTERNALERROR, 61.x.x.x | The responder responded with an internalError message indicating that it encountered an internal error. |
ERR_OCSP_STAT_MALFORMEDREQUEST, 60.x.x.x | The responder responded with a malformedRequest message indicating that edge server's message didn't conform to the OCSP syntax. |
ERR_OCSP_STAT_SIGREQUIRED, 63.x.x.x | The responder responded with a sigRequired message indicating that the edge server should sign the request. Edge servers don't support signing of the request at this point. |
ERR_OCSP_STAT_TRYLATER, 62.x.x.x | The responder responded with the tryLater message indicating that the edge server should retry later. Edge serves retry against a secondary responder (if any) or when the user makes another request. |
ERR_OCSP_STAT_UNAUTHORIZED, 64.x.x.x | The responder responded with the unauthorized message indicating that the edge server is not authorized to make a query against the given responder. |
ERR_OCSP_STAT_UNKNOWN, 65.x.x.x | The responder responded with a message that the edge server didn't understand. |
ERR_OCSP_THIS_UPD_AHEAD_OF_NEXT, 90.x.x.x | The this-update field was ahead of the next-update field. |
ERR_OCSP_THIS_UPD_INVALID, 84.x.x.x | The this-update field couldn't be parsed. |
ERR_OCSP_THIS_UPD_MISSING, 83.x.x.x | The this-update field was missing from the response. |
ERR_OCSP_THIS_UPD_TOO_AHEAD, 86.x.x.x | The this-update field was way passed the current time based on the security.essl.slot-assignment.client-cert. ocsp.responder.this-upd-allowed-future-diff setting. |
ERR_OCSP_THIS_UPD_TOO_OLD, 85.x.x.x | The this-update field was too old based on the security.essl.slot-assignment.client-cert. ocsp.responder.this-upd-allowed-past-diff setting. |
ERR_OCSP_VERIFY, 68.x.x.x | The verification of the basicResponse failed. Check cache.log for failure details. |
ERR_ORIGIN_HOST_LOOP, 197.x.x.x | The origin hostname that the edge server was about to go forward to matches the name in the client request Host header indicating a loop in the forward logic. This behavior is controlled by the metadata tag network:dns.rollback-origin-host-loop-check. |
ERR_OUT_OF_RESOURCES, 217.x.x.x | Internal error. For more details, contact the support team. |
ERR_OUTPUT_FILTER_EXCEED_MAX_BUF_SIZE, 241.x.x.x | Internal error. For more details, contact the support team. |
ERR_P2G_AUTH, 213.x.x.x | Partner Authentication failures. The possible refined error messages for this error currently are: - scc_partnerauth_failed, when an SCC log line POST is rejected because partner authentication failed. - scc_partnerauth_notenabled, when an SCC log line POST is rejected because partner authentication is not enabled. |
ERR_PARTIAL_FWD_REJECT, 113.x.x.x | Read error happened due to partial forward reject. |
ERR_PLAYLIST_MODIFICATION, 220.x.x.x | Internal error. For more details, contact the support team. |
ERR_POC, 163.x.x.x | Internal error. For more details, contact the support team. |
ERR_POC_FWD_ABORT, 159.x.x.x | Failed to fetch a fragment most likely due to forward server breaking off. Check the 'f' line for details. The fragment's status code is set to 503 in this case. This could also occur when an incorrect client range makes it to the forward side of the connecting client. If cache:poc2.hide-forward-errs-from-user is on, this error won't show in the logs. |
ERR_POC_FWD_AK_GZIPPED, 153.x.x.x | The response had the X-Ak-Gzip-Downstream header indicating that a peer or parent edge server compressed the response. |
ERR_POC_FWD_BAD_RLEN, 139.x.x.x | Unexpected length of the range in the content-range response header. |
ERR_POC_FWD_CANT_CREATE_MS, 156.x.x.x | Failed to establish a master entry due to some error on the forward side. The master is converted to a regular entry with a 503 HTTP status code. |
ERR_POC_FWD_COBRA_FIRSTFRAG_ERROR, 246.x.x.x | Internal error. For more details, contact the support team. |
ERR_POC_FWD_CONTENT_MD5_CHANGED, 191.x.x.x | Internal error. For more details, contact the support team. |
ERR_POC_FWD_CONTENT_MD5_NONE, 192.x.x.x | Internal error. For more details, contact the support team. |
ERR_POC_FWD_DCA_OUTPUT, 134.x.x.x | X-Akamai-DCA-Output-Maxage was present in the response. |
ERR_POC_FWD_ETAG_BAD, 147.x.x.x | cache.poc2.trust-etag is on and the ETag in the response had a non-HTTP compliant format. The value has to be surrounded by double quotes with an optional "W/" indicating weak. ETag. |
ERR_POC_FWD_ETAG_CHANGED, 151.x.x.x | The object consistency verification failed because the ETag is different on the current master and a fragment. This may mean that one of the ETags was either different or badly formatted or the ETag was missing from one of them. |
ERR_POC_FWD_ETAG_NONE, 145.x.x.x | cache.poc2.trust-etag is on and there was no ETag in the response. |
ERR_POC_FWD_ETAG_WEAK, 146.x.x.x | cache.poc2.trust-etag is on and the ETag in the response was tagged as weak. |
ERR_POC_FWD_FRAG_ABORT, 157.x.x.x | Failed to fetch a fragment most likely due to forward server breaking off. Check the 'f' line for details. The fragment's status code is set to 503 in this case. This could also occur when an incorrect client range makes it to the forward side of the edge server. |
ERR_POC_FWD_G2G_ABORT, 155.x.x.x | The connection had to be interrupted because the in-coming client is another edge server and the origin drops the connection after the response was being received. |
ERR_POC_FWD_GZIPPED, 135.x.x.x | The response was compressed. |
ERR_POC_FWD_LASTMOD_BAD, 149.x.x.x | cache:poc2.trust-lastmod is on and the Last-Modified header in the response had an incorrect format. On the 'f' line, they're always printed time when the inconsistent fragment was encountered and on the r line whether the connection was interrupted. Otherwise, the 'r' line have a status code indicating that possibly an inconsistent object was served. |
ERR_POC_FWD_LASTMOD_CHANGED, 152.x.x.x | The object consistency verification failed because the last-modified time is different between on the current master and a fragment. This may mean that one of the last-modified times was different or badly formatted or the last-modified time was missing from one of them. |
ERR_POC_FWD_LASTMOD_NONE, 148.x.x.x | cache:poc2.trust-lastmod is on and there was no Last-Modified header in the response. |
ERR_POC_FWD_LEN_MISMATCH, 140.x.x.x | The content-length header didn't match the number of bytes given with the content-range header. |
ERR_POC_FWD_MS_NONCH, 142.x.x.x | The response to the initial POC range request indicates the object is not cacheable. Either this object is misconfigured on the origin or POC shouldn't be applied to it. |
ERR_POC_FWD_NO_CONTLEN, 133.x.x.x | The response had no content-length header. |
ERR_POC_FWD_NO_ELEN, 137.x.x.x | The entity-length field was not a specific number in the content-range response header. |
ERR_POC_FWD_NO_OFFSET, 138.x.x.x | The content-range header had no beginning offset. |
ERR_POC_FWD_NO_RANGE, 136.x.x.x | The response had no content-range header. |
ERR_POC_FWD_NOT_206, 132.x.x.x | The HTTP response code was not 206 Partial Content. |
ERR_POC_FWD_OBJ_SIZE_CHANGED, 150.x.x.x | The object consistency verification failed because the object size is different on the current master and a fragment. |
ERR_POC_FWD_OBJ_TOO_BIG, 144.x.x.x | The response object is larger than what is permitted by the configuration settings. |
ERR_POC_FWD_OBJ_TOO_SMALL, 143.x.x.x | The response object is smaller than what is permitted by the configuration settings. |
ERR_POC_FWD_OFFSET_MISMATCH, 141.x.x.x | The beginning offset of the content-range response header didn't match the beginning offset of the range request header. |
ERR_POC_FWD_TR_ENC, 154.x.x.x | The response was transfer-encoded. The edge server retries with a regular forward request. |
ERR_POC_INTEG_NO_PUBLIC_ORIG_ENTRY, 243.x.x.x | Internal error. For more details, contact the support team. |
ERR_POC_MS_FRAG_SIZE_CHANGED, 129.x.x.x | The client connection was interrupted because all of the following cases occurred: - The master entry the client was attached to became private, the object got purged or revalidated and the TTL expired. - More fragments on behalf of the users attached to the private master had to be downloaded. - The newly created public master had a different fragment size. |
ERR_POC_MS_NO_PUBLIC_ENTRY, 131.x.x.x | Internal error. For more details, contact the support team. |
ERR_POC_MS_OBJ_SIZE_CHANGED | Internal error. For more details, contact the support team. |
ERR_POC_MS_POC_OFF, 130.x.x.x | The client connection was interrupted because all of the following cases occurred: - The master entry the client was attached to became private, the object got purged or revalidated and the TTL expired. - More fragments on behalf of the users attached to the private master had to be downloaded. - The newly created public StoreEntry was not a POC entry. |
ERR_POC_TC_FP, 158.x.x.x | The request was for a TC 2/3 object and POC2 was on and they are not compatible. |
ERR_PREFETCH_LIMIT, 93.x.x.x | One of the limits on the number of forward requests based on the Prefetching feature was exceeded. The error can apply to edge servers or to the customer. |
ERR_PURGE_SEQ_OUT_OF_DATE, 128.x.x.x | The forward connection to the origin was interrupted due to a purge sequence number mismatch. |
ERR_QUEUE_ENQ, 118.x.x.x | Write error happened due to the enqueuing the current request failure. |
ERR_QUEUE_FOPEN, 115.x.x.x | Internal error. For more details, contact the support team. |
ERR_QUEUE_MKDIR, 114.x.x.x | Write error happened due to the Mkdir in the client queue code failure. |
ERR_QUEUE_POST_TOO_BIG, 117.x.x.x | Write error happened due to too big POST body for the client queue. |
ERR_QUEUE_WRITE, 116.x.x.x | Write error happened due to the write file in the client queue code failure. |
ERR_RAW_ABORT, 160.x.x.x | Internal error. For more details, contact the support team. |
ERR_READ_ERROR, 3.x.x.x | The TCP connection from the edge server to the origin server was broken before the headers and object were successfully downloaded. If this happens even though the origin is healthy, you can try lowering the persistent connection timeout to be lower than origin’s setting, or you can try disabling the persistent connection feature on the edge server. |
ERR_READ_TIMEOUT, 1.x.x.x | The forward connection to the origin server from the edge server timed out. |
ERR_RESOURCE_INTEGRITY_FAILED, 225.x.x.x | Internal error. For more details, contact the support team. |
ERR_RSYNC_OBSOLETE, 106.x.x.x | Internal error. For more details, contact the support team. |
ERR_SHUTTING_DOWN, 5.x.x.x | The edge server received the shutdown order and is shutting down. |
ERR_SILVERLIGHT, 201.x.x.x | Internal error. For more details, contact the support team. |
ERR_SOCKET_FAILURE, 10.x.x.x | Internal error. For more details, contact the support team. |
ERR_SSL_CONNECT_TIMEOUT, 98.x.x.x | The SSL connection to the origin server from the edge server timed out. |
ERR_SSL_HTTP2_NO_RENEGOTIATION, 224.x.x.x | Internal error. For more details, contact the support team. |
ERR_SSL_INSECURE_RENEGOTIATION, 189.x.x.x | Connection interrupted with HTTP_FORBIDDEN because of not secure ESSL client-side renegotiation. |
ERR_SSL_POST_RENEG, 125.x.x.x | SSL client-side session renegotiation was requested under a POST request with the feature being turned off. |
ERR_SSL_POST_RENEG_TOO_BIG, 173.x.x.x | SSL client-side session renegotiation was requested under a POST request but the POST body size was greater than permitted by the configured settings. |
ERR_SSL_RENEG, 176.x.x.x | Internal error. For more details, contact the support team. |
ERR_SSL_TLS_SECURITY_EXT, 190.x.x.x | Connection interrupted with HTTP_FORBIDDEN because of security:enforce-tls-security-extension.* on and the TLS secure renegotiation extension not in effect. |
ERR_STORE_COPY, 110.x.x.x | Internal error. For more details, contact the support team. |
ERR_STORE_HTTP_STATUS_NONE, 240.x.x.x | The response had no status code. |
ERR_STREAMING_BAD_CONNECTION, 208.x.x.x | Internal error. For more details, contact the support team. |
ERR_STREAMING_MULTI, 216.x.x.x | Internal error. For more details, contact the support team. |
ERR_STREAMING_VERIFICATION_FAILED, 188.x.x.x | Internal error. For more details, contact the support team. |
ERR_SUREROUTE_DNS_FAIL, 100.x.x.x | Akaroute RProxy Marker error. The DNS resolution for a parent came back as 0.0.0.1 or 0.0.0.2. |
ERR_SWAPMETA_FAIL, 209.x.x.x | Internal error. For more details, contact the support team. |
ERR_SWAPMETA_PARSE_FAIL, 211.x.x.x | Internal error. For more details, contact the support team. |
ERR_TPCA, 204.x.x.x | Internal error. For more details, contact the support team. |
ERR_TRANSFORMATION_POOL, 205.x.x.x | Edge server encountered an error related to the thread pool that performs content transformations. There should be currently no way for this error to actually occur. Problems with transformed content trigger ERR_TRANSFORMING instead, the most important types of which are documented above. |
ERR_TRANSFORMING, 200.x.x.x | Connection interrupted. The edge server encountered an error in the midst of transforming content after it had already sent at least one byte of data to the client. The message after the '|' refines the nature of the error. |
ERR_UITS_BAD_REQUEST, 196.x.x.x | Internal error. For more details, contact the support team. |
ERR_UNSUP_REQ, 8.x.x.x | Unsupported request. |
ERR_URL_DIS_AUTH, 50.x.x.x | URL-based edge authorization feature rejected this request. |
ERR_URN_RESOLVE, 16.x.x.x | Internal error. For more details, contact the support team. |
ERR_WAR_ABORT, 107.x.x.x | The WAR file was interrupted. |
ERR_WEBSOCKET_PRUNE, 229.x.x.x | Internal error. For more details, contact the support team. |
ERR_WEBSOCKET_READ_TIMEOUT, 228.x.x.x | Internal error. For more details, contact the support team. |
ERR_WIN32_READ_ERR, 123.x.x.x | The forward connection to the origin server broke. |
ERR_WM_ACCESS_DENIED, 171.x.x.x | Watermark Authentication failed. |
ERR_WRITE_ERROR, 4.x.x.x | Unable to close the socket to the client. |
ERR_ZERO_SIZE_OBJECT, 15.x.x.x | A response from the origin server has zero length. |
GET_FILTERED_OBJ, 255.x.x.x | Internal error. For more details, contact the support team. |
ICP_PUBLIC_EARLY_RESPONSE, 184.x.x.x | Internal error. For more details, contact the support team. |
STORE_ENTRY_LOOP_DETECT, 185.x.x.x | Internal error. For more details, contact the support team. |
STREAMING_BAD_REQUEST, 181.x.x.x | Internal error. For more details, contact the support team. |
STREAMING_NOT_FOUND, 183.x.x.x | Internal error. For more details, contact the support team. |
STREAMING_UNAUTHORIZED, 182.x.x.x | Internal error. For more details, contact the support team. |
Updated 2 days ago
Did this page help you?