에러 코드 검색
HTTP, PostgreSQL, MySQL 에러 코드를 검색하고 해결 방법을 확인합니다
The request succeeded.
The request succeeded and a new resource was created.
The request succeeded but returns no content.
The URL has been permanently moved.
The URL has been temporarily moved.
Resource not modified since last request.
The server cannot process the request due to client error.
💡 Check request syntax, headers, and body format.
Authentication is required and has failed or not been provided.
💡 Provide valid authentication credentials.
The server understood the request but refuses to authorize it.
💡 Check user permissions and access rights.
The requested resource could not be found.
💡 Verify the URL is correct and the resource exists.
The request method is not supported for this resource.
💡 Use a different HTTP method (GET, POST, PUT, DELETE).
The server timed out waiting for the request.
💡 Retry the request or increase timeout settings.
The request conflicts with the current state of the resource.
💡 Resolve the conflict and retry.
The request entity is larger than the server will process.
💡 Reduce the size of the request body.
The media format is not supported.
💡 Use a supported Content-Type header.
The request was well-formed but had semantic errors.
💡 Check the request body for validation errors.
The user has sent too many requests in a given time.
💡 Implement rate limiting and add delays between requests.
The server encountered an unexpected condition.
💡 Check server logs for the root cause.
The server does not support the functionality required.
💡 Use a different endpoint or implement the feature.
The server received an invalid response from an upstream server.
💡 Check the upstream server status and connectivity.
The server is not ready to handle the request.
💡 Wait and retry, or check server health.
The gateway did not receive a response from the upstream server.
💡 Check upstream server performance and network.
Duplicate key value violates unique constraint.
💡 Ensure the value is unique or use ON CONFLICT clause.
Foreign key constraint violation.
💡 Ensure referenced row exists before inserting.
NOT NULL constraint violation.
💡 Provide a value for the NOT NULL column.
CHECK constraint violation.
💡 Ensure the value satisfies the CHECK constraint.
SQL syntax error.
💡 Check SQL syntax near the error position.
Table does not exist.
💡 Verify table name and run migrations if needed.
Column does not exist.
💡 Check column name spelling and case sensitivity.
Database already exists.
💡 Use a different name or drop existing database.
Table already exists.
💡 Use IF NOT EXISTS or drop existing table.
Disk space is exhausted.
💡 Free up disk space or increase storage.
Server ran out of memory.
💡 Increase memory or optimize queries.
Query was cancelled by statement_timeout.
💡 Optimize query or increase timeout.
Invalid password for user.
💡 Check credentials for the database user.
Database does not exist.
💡 Create the database or check the name.
Connection to the server was lost.
💡 Check network and server status.
Transaction could not serialize access.
💡 Retry the transaction.
Deadlock detected between transactions.
💡 Restructure transactions to avoid deadlock.
Access denied for user.
💡 Check username, password, and host permissions.
Unknown database.
💡 Create the database or check spelling.
Unknown column in field list.
💡 Check column name and table structure.
Duplicate entry for key.
💡 Use INSERT IGNORE or ON DUPLICATE KEY UPDATE.
SQL syntax error.
💡 Check SQL syntax near the error position.
Table does not exist.
💡 Create the table or check table name.
Cannot add foreign key constraint.
💡 Check parent table structure and data types.
Cannot delete or update a parent row.
💡 Delete child rows first or use ON DELETE CASCADE.
Foreign key constraint fails on delete/update.
💡 Handle child records before modifying parent.
Foreign key constraint fails on insert/update.
💡 Ensure parent row exists first.
Cannot connect to local MySQL server.
💡 Check if MySQL is running and socket is correct.
Cannot connect to MySQL server on host.
💡 Check server address, port, and firewall.
MySQL server has gone away.
💡 Check wait_timeout and max_allowed_packet.
Lock wait timeout exceeded.
💡 Optimize queries or increase innodb_lock_wait_timeout.
Deadlock found when trying to get lock.
💡 Retry transaction or restructure queries.
에러 코드 데이터베이스
- HTTP 상태 코드 (1xx ~ 5xx)
- PostgreSQL SQLSTATE 코드
- MySQL 에러 번호 및 설명
관련 도구
Workflow 전체 보기함께 쓰면 좋은 도구를 확인하세요.