Access denied for user...

확인 범위

이 문서는 화면 또는 로그에 표시된 Access denied for user... 문구가 MariaDB Documentation 공식 원문의 항목과 일치하는지 확인합니다.

원문 발췌

S error codes: Example output: Causes & Solutions By default, MariaDB often does not accept remote TCP/IP connections, or is bound only to localhost (127.0.0.1). Solution: See Configuring MariaDB for Remote Client Access for detailed instructions on how to enable remote connections by adjusting the bind-address server variable and ensuring user accounts are configured correctly for remote hosts. Authentication Problems Symptoms Connection is established, but authentication fails (for instance, "Access denied for user..."). Causes & Solutions Unix Socket Authentication: On Unix-like systems, the unix_socket authentication plugin is enabled by default for local connections via the Unix socket file. This plugin uses operating system user credentials. See the unix_socket authentication plugin documentation for connection instructions and how to switch to password-based authentication if needed. For an overview of authentication changes in MariaDB 10.4, see Authentication from MariaDB 10.4. Incorrect Username/Host Combination: Authentication is specific to a username@host combination. For example, 'user1'@'localhost' is distinct from 'user1'@'166.78.144.191'. Ensure the user account exists for the host from which you are connecting. See GRANT for details on granting permissions. Password Hashing: When setting or changing passwords using SET PASSWORD, ensure the PASSWORD() function is used if the server expects hashed passwords. Example: SET PASSWORD FOR 'bob'@'%.loc.gov' = PASSWORD('newpass'); Rather than: SET PASSWORD FOR 'bob'@'%.loc.gov' = 'newpass'; (which might store the password as plain text, potentially leading to issues depending on the authentication plugin). Problems Exporting Query Results or Loading Data Symptoms You can run regular queries, but get authentication or permission errors when using SELECT ... INTO OUTFILE, SELECT ... INTO DUMPFILE, or LOAD DATA INFILE. Causes & Solutions These operations require the FILE privilege on the server. Solution: Grant the necessary FILE privilege to the user. See the GRANT article. Access Denied to a Specific Database Symptoms You can connect to the MariaDB server, but attempting to issue the USE command or query a specific database results in an error: Or, connecting with mariadb -u user -p db1 works, but mariadb -u user -p db2 fails for db2. Causes & Solutions The user account has not been granted sufficient privileges for that particular database. Solution: Grant the required privileges (e.g., SELECT, INSERT, etc.) on the specific database to the user. See GRANT. Issues Due to Option Files or Environment Variables Symptoms Unexpected connection behavior, or parameter usage that you didn't explicitly provide on the command line. Causes & Solutions Option files (for instance, my.cnf, .my.ini) or environment variables (for instance, MYSQL_HOST) might be supplying incorrect parameters, or overriding connection parameters. Troubleshooting: Check the values in any option files read by your client. See Configuring MariaDB with

확인 절차

1. 현재 화면 또는 로그에서 Access denied for user... 문구를 확인합니다.
2. 위 원문 발췌와 문구를 비교합니다.
3. 문구가 일치하면 이 문서의 출처 링크에서 적용 환경과 원문 전체를 확인합니다.

주의

이 문서는 문구 식별 범위로 제한합니다. 출처가 직접 설명하지 않는 원인, 설정 변경, 권한 변경 또는 복구 절차를 이 문서만으로 실행하지 마십시오.