400 Bad Request400 Bad Request — Nginx Bad Request
Nginx rejected the client request due to a malformed HTTP request.
Durchstöbern Sie alle 40 Nginx-Fehler-Fehlercodes mit Ursachen, Lösungen und Beispielen.
400 Bad RequestNginx rejected the client request due to a malformed HTTP request.
403 ForbiddenNginx denied access to the requested resource.
404 Not FoundThe requested resource was not found on the server.
413 Request Entity Too LargeThe request body exceeds the maximum size allowed by Nginx.
414 URI Too LongThe request URI exceeds the maximum length Nginx will process.
429 Too Many RequestsThe client has sent too many requests in a given time period.
494 Request Header Too LargeThe request headers exceed Nginx's maximum header buffer size.
495 SSL Certificate ErrorThe client SSL certificate presented an error.
496 SSL Certificate RequiredA client certificate is required but was not provided.
497 HTTP to HTTPSA plain HTTP request was sent to the HTTPS port.
499 Client Closed RequestThe client closed the connection before the server sent a response.
500 Internal Server ErrorAn unexpected error occurred within Nginx or the upstream application.
502 Bad GatewayNginx received an invalid response from the upstream server.
503 Service UnavailableThe server is temporarily unable to handle the request.
504 Gateway TimeoutNginx timed out waiting for a response from the upstream server.
upstream timed outNginx timed out while waiting for the upstream server to respond.
connect() failed (111: Connection refused)Nginx could not connect to the upstream server.
worker_connections are not enoughThe Nginx worker process has reached its maximum number of connections.
SSL_do_handshake() failedThe SSL/TLS handshake with a client or upstream server failed.
open() failed (13: Permission denied)Nginx cannot read the file due to filesystem permissions.
open() failed (2: No such file or directory)Nginx cannot find the requested file.
rewrite or internal redirection cycleNginx detected an infinite redirect or rewrite loop.
no resolver defined to resolveNginx needs to resolve a hostname but no DNS resolver is configured.
too many open filesNginx has reached the maximum number of open file descriptors.
upstream prematurely closed connectionThe upstream server closed the connection before sending a complete response.
recv() failed (104: Connection reset by peer)The client reset the connection during data transfer.
conflicting server nameTwo or more server blocks use the same server_name.
could not build server_names_hashNginx cannot build the server names hash table.
bind() to 0.0.0.0:80 failed (98: Address already in use)Nginx cannot bind to the requested address and port.
invalid PID numberThe Nginx PID file contains an invalid process ID.
host not found in upstreamNginx could not resolve the hostname specified in the upstream block.
no live upstreams while connecting to upstreamAll upstream servers in the pool are marked as unavailable.
SSL: error:0B080074:x509 certificate routinesAn SSL certificate validation error occurred.
client body temp file write errorNginx cannot write the client request body to a temporary file.
an upstream response is buffered to a temporary fileThe upstream response is being buffered to disk because it exceeds memory buffers.
upstream sent too big header while reading response header from upstreamThe upstream server sent response headers larger than Nginx's buffer.
301 Moved PermanentlyNginx is redirecting the client to a new URL permanently.
304 Not ModifiedThe resource has not been modified since the client's last request.
408 Request TimeoutThe client did not send a complete request within the timeout period.
no servers are inside upstreamThe upstream block has no servers defined.