Networking errors

Networking errors usually involve ports, sockets, connectivity, DNS resolution, or host-to-service communication problems.

Active Directory AWS Docker GCP HTTP npm pip

Back to all categories

1908

Active Directory operation failed because it could not find the domain controller for the domainActive Directory Replication

1753

Active Directory replication failed because no endpoints were available from the endpoint mapperActive Directory Replication

8524

Active Directory replication failed because of a DNS lookup failureActive Directory Replication

1727

Active Directory replication failed because the remote procedure call failed and did not executeActive Directory Replication

1256

Active Directory replication failed because the remote system is not availableActive Directory Replication

1722

Active Directory replication failed because the RPC server is unavailableActive Directory Replication

504 Gateway Timeout

AWS Management Console returned 504 Gateway TimeoutAWS Management Console

RequestEntityTooLargeException

AWS rejected the request because the request entity is too largeGeneral

RequestAbortedException

AWS request was aborted before the service returned a replyGeneral

RequestTimeoutException

AWS timed out while reading the requestGeneral

Waiting for certificate provisioning. You must configure your DNS records for certificate issuance to begin.

Cloud Run custom domain is waiting for certificate provisioningCloud Run

HTTP 404: Not Found

Cloud Run returned HTTP 404 Not FoundCloud Run

port is already allocated

Docker could not bind the published port because it is already allocatedDocker

0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports.

GKE could not schedule the pod because nodes did not have free requested pod portsGKE

i/o timeout

GKE image pull failed with i/o timeoutGKE

408 Request Timeout

HTTP 408 Request TimeoutHTTP Status Codes

413 Content Too Large

HTTP 413 Content Too LargeHTTP Status Codes

414 URI Too Long

HTTP 414 URI Too LongHTTP Status Codes

429 Too Many Requests

HTTP 429 Too Many RequestsHTTP Status Codes

502 Bad Gateway

HTTP 502 Bad GatewayHTTP Status Codes

504 Gateway Timeout

HTTP 504 Gateway TimeoutHTTP Status Codes

npm only uses git: and ssh+git: URLs for GitHub repos, breaking proxies

npm GitHub git and ssh URLs are breaking behind a proxynpm

SSL-intercepting proxy

npm is behind an SSL-intercepting proxynpm

CERT_UNTRUSTED / UNABLE_TO_VERIFY_LEAF_SIGNATURE

npm SSL certificate is untrusted or leaf signature cannot be verifiednpm

SELF_SIGNED_CERT_IN_CHAIN

npm SSL self signed certificate in chainnpm

SSL23_GET_SERVER_HELLO:unknown protocol

npm SSL unknown protocol errornpm

There was a problem confirming the ssl certificate

pip could not confirm the SSL certificate for the package index connectionpip

CERTIFICATE_VERIFY_FAILED

pip failed TLS certificate verificationpip

Networking Errors | Error Atlas