连接MySQL报错，is not allowed to connect to this MySQL server

题目描述：

           本机装的MySQL数据库，本机可以正常连接，其他呆板访问报错，is not allowed to connect to this MySQL server，防火墙等其他策略均设置没题目。
  

---

 解决方案：
           出现该题目标原因是，MySQL数据库只答应自身所在的本呆板连接，不答应远程连接。
  1、在MySQL所在服务器上使用命令登录到MySQL数据库中

1. mysql -u root -p

复制代码

2、选择mysql数据库，并查询权限

1. use mysql;
3. select host from user where user='root';

复制代码

可以看到，实行查询语句后得到的数据效果中 host 的值是 localhost
我们实行update语句修改权限

1. update user set host = '%' where user ='root';

复制代码

3、刷新设置

1. flush privileges;

复制代码

再次实行查询权限语句

1. select host from user where user='root';

复制代码

可以看到，已经修改成功
4、末了再次用其他呆板连接MySQL数据库，可以连接成功
   DBMS: MySQL (版本 5.7.41)
区分大小写: 平凡形式=lower, 分隔形式=lower
驱动步伐: MySQL Connector/J (版本 mysql-connector-java-8.0.25 (Revision: 08be9e9b4cba6aa115f9b27b215887af40b159e0)，JDBC4.2)
  Ping: 29毫秒
SSL: yes
  

---

1. <?xml version="1.0" encoding="UTF-8"?>
3. <!--
4. Licensed to the Apache Software Foundation (ASF) under one
5. or more contributor license agreements.  See the NOTICE file
6. distributed with this work for additional information
7. regarding copyright ownership.  The ASF licenses this file
8. to you under the Apache License, Version 2.0 (the
9. "License"); you may not use this file except in compliance
10. with the License.  You may obtain a copy of the License at
11.     http://www.apache.org/licenses/LICENSE-2.0
12. Unless required by applicable law or agreed to in writing,
13. software distributed under the License is distributed on an
14. "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
15. KIND, either express or implied.  See the License for the
16. specific language governing permissions and limitations
17. under the License.
18. -->
20. <!--
21. | This is the configuration file for Maven. It can be specified at two levels:
22. |
23. |  1. User Level. This settings.xml file provides configuration for a single user,
24. |                 and is normally provided in ${user.home}/.m2/settings.xml.
25. |
26. |                 NOTE: This location can be overridden with the CLI option:
27. |
28. |                 -s /path/to/user/settings.xml
29. |
30. |  2. Global Level. This settings.xml file provides configuration for all Maven
31. |                 users on a machine (assuming they're all using the same Maven
32. |                 installation). It's normally provided in
33. |                 ${maven.conf}/settings.xml.
34. |
35. |                 NOTE: This location can be overridden with the CLI option:
36. |
37. |                 -gs /path/to/global/settings.xml
38. |
39. | The sections in this sample file are intended to give you a running start at
40. | getting the most out of your Maven installation. Where appropriate, the default
41. | values (values used when the setting is not specified) are provided.
42. |
43. |-->
44. <settings xmlns="http://maven.apache.org/SETTINGS/1.2.0"
45.           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
46.           xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 https://maven.apache.org/xsd/settings-1.2.0.xsd">
47.   <!-- localRepository
48.    | The path to the local repository maven will use to store artifacts.
49.    |
50.    | Default: ${user.home}/.m2/repository
51.   <localRepository>/path/to/local/repo</localRepository>
52.   -->
54.   <!-- interactiveMode
55.    | This will determine whether maven prompts you when it needs input. If set to false,
56.    | maven will use a sensible default value, perhaps based on some other setting, for
57.    | the parameter in question.
58.    |
59.    | Default: true
60.   <interactiveMode>true</interactiveMode>
61.   -->
63.   <!-- offline
64.    | Determines whether maven should attempt to connect to the network when executing a build.
65.    | This will have an effect on artifact downloads, artifact deployment, and others.
66.    |
67.    | Default: false
68.   <offline>false</offline>
69.   -->
71.   <!-- pluginGroups
72.    | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
73.    | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
74.    | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
75.    |-->
76.   <pluginGroups>
77.     <!-- pluginGroup
78.      | Specifies a further group identifier to use for plugin lookup.
79.     <pluginGroup>com.your.plugins</pluginGroup>
80.     -->
81.   </pluginGroups>
83.   <!-- proxies
84.    | This is a list of proxies which can be used on this machine to connect to the network.
85.    | Unless otherwise specified (by system property or command-line switch), the first proxy
86.    | specification in this list marked as active will be used.
87.    |-->
88.   <proxies>
89.     <!-- proxy
90.      | Specification for one proxy, to be used in connecting to the network.
91.      |
92.     <proxy>
93.       <id>optional</id>
94.       <active>true</active>
95.       <protocol>http</protocol>
96.       <username>proxyuser</username>
97.       <password>proxypass</password>
98.       <host>proxy.host.net</host>
99.       <port>80</port>
100.       <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
101.     </proxy>
102.     -->
103.   </proxies>
105.   <!-- servers
106.    | This is a list of authentication profiles, keyed by the server-id used within the system.
107.    | Authentication profiles can be used whenever maven must make a connection to a remote server.
108.    |-->
109.   <servers>
110.     <!-- server
111.      | Specifies the authentication information to use when connecting to a particular server, identified by
112.      | a unique name within the system (referred to by the 'id' attribute below).
113.      |
114.      | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
115.      |       used together.
116.      |
117.     <server>
118.       <id>deploymentRepo</id>
119.       <username>repouser</username>
120.       <password>repopwd</password>
121.     </server>
122.     -->
124.     <!-- Another sample, using keys to authenticate.
125.     <server>
126.       <id>siteServer</id>
127.       <privateKey>/path/to/private/key</privateKey>
128.       <passphrase>optional; leave empty if not used.</passphrase>
129.     </server>
130.     -->
131.   </servers>
133.   <!-- mirrors
134.    | This is a list of mirrors to be used in downloading artifacts from remote repositories.
135.    |
136.    | It works like this: a POM may declare a repository to use in resolving certain artifacts.
137.    | However, this repository may have problems with heavy traffic at times, so people have mirrored
138.    | it to several places.
139.    |
140.    | That repository definition will have a unique id, so we can create a mirror reference for that
141.    | repository, to be used as an alternate download site. The mirror site will be the preferred
142.    | server for that repository.
143.    |-->
144.   <mirrors>
145.     <!-- mirror
146.      | Specifies a repository mirror site to use instead of a given repository. The repository that
147.      | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
148.      | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
149.      |
150.     <mirror>
151.       <id>mirrorId</id>
152.       <mirrorOf>repositoryId</mirrorOf>
153.       <name>Human Readable Name for this Mirror.</name>
154.       <url>http://my.repository.com/repo/path</url>
155.     </mirror>
156.      -->
157.     <mirror>
158.       <id>maven-default-http-blocker</id>
159.       <mirrorOf>external:http:*</mirrorOf>
160.       <name>Pseudo repository to mirror external repositories initially using HTTP.</name>
161.       <url>http://0.0.0.0/</url>
162.       <blocked>true</blocked>
163.     </mirror>
164.   </mirrors>
166.   <!-- profiles
167.    | This is a list of profiles which can be activated in a variety of ways, and which can modify
168.    | the build process. Profiles provided in the settings.xml are intended to provide local machine-
169.    | specific paths and repository locations which allow the build to work in the local environment.
170.    |
171.    | For example, if you have an integration testing plugin - like cactus - that needs to know where
172.    | your Tomcat instance is installed, you can provide a variable here such that the variable is
173.    | dereferenced during the build process to configure the cactus plugin.
174.    |
175.    | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
176.    | section of this document (settings.xml) - will be discussed later. Another way essentially
177.    | relies on the detection of a system property, either matching a particular value for the property,
178.    | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
179.    | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
180.    | Finally, the list of active profiles can be specified directly from the command line.
181.    |
182.    | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
183.    |       repositories, plugin repositories, and free-form properties to be used as configuration
184.    |       variables for plugins in the POM.
185.    |
186.    |-->
187.   <profiles>
188.     <!-- profile
189.      | Specifies a set of introductions to the build process, to be activated using one or more of the
190.      | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
191.      | or the command line, profiles have to have an ID that is unique.
192.      |
193.      | An encouraged best practice for profile identification is to use a consistent naming convention
194.      | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
195.      | This will make it more intuitive to understand what the set of introduced profiles is attempting
196.      | to accomplish, particularly when you only have a list of profile id's for debug.
197.      |
198.      | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
199.     <profile>
200.       <id>jdk-1.4</id>
201.       <activation>
202.         <jdk>1.4</jdk>
203.       </activation>
204.       <repositories>
205.         <repository>
206.           <id>jdk14</id>
207.           <name>Repository for JDK 1.4 builds</name>
208.           <url>http://www.myhost.com/maven/jdk14</url>
209.           <layout>default</layout>
210.           <snapshotPolicy>always</snapshotPolicy>
211.         </repository>
212.       </repositories>
213.     </profile>
214.     -->
216.     <!--
217.      | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
218.      | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
219.      | might hypothetically look like:
220.      |
221.      | ...
222.      | <plugin>
223.      |   <groupId>org.myco.myplugins</groupId>
224.      |   <artifactId>myplugin</artifactId>
225.      |
226.      |   <configuration>
227.      |     <tomcatLocation>${tomcatPath}</tomcatLocation>
228.      |   </configuration>
229.      | </plugin>
230.      | ...
231.      |
232.      | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
233.      |       anything, you could just leave off the <value/> inside the activation-property.
234.      |
235.     <profile>
236.       <id>env-dev</id>
237.       <activation>
238.         <property>
239.           <name>target-env</name>
240.           <value>dev</value>
241.         </property>
242.       </activation>
243.       <properties>
244.         <tomcatPath>/path/to/tomcat/instance</tomcatPath>
245.       </properties>
246.     </profile>
247.     -->
248.   </profiles>
250.   <!-- activeProfiles
251.    | List of profiles that are active for all builds.
252.    |
253.   <activeProfiles>
254.     <activeProfile>alwaysActiveProfile</activeProfile>
255.     <activeProfile>anotherAlwaysActiveProfile</activeProfile>
256.   </activeProfiles>
257.   -->
258. </settings>

复制代码

  1。 改表法。可能是你的帐号不答应从远程登陆，只能在localhost。这个时间只要在localhost的那台电脑，登入mysql后，更改 "mysql" 数据库里的 "user" 表里的 "host" 项，从"localhost"改称"%"
  Sql代码 复制代码
     1. mysql -u root -pvmwaremysql>use mysql; 
     2. mysql>update user set host = '%' where user = 'root'; 
     3. mysql>select host, user from user; 
  2. 授权法。例如，你想myuser使用mypassword从任何主机连接到mysql服务器的话。
  Sql代码 复制代码
    1. GRANT ALL PRIVILEGES ON *.* TO 'myuser'@'%' IDENTIFIED BY 'mypassword' WITH
        GRANT OPTION;  
    2.FLUSH   PRIVILEGES; 

免责声明：如果侵犯了您的权益，请联系站长，我们会及时删除侵权内容，谢谢合作！更多信息从访问主页：qidao123.com:ToB企服之家，中国第一个企服评测及商务社交产业平台。

继续阅读请点击广告