授权方式解决Host '192.168.1.180' is not allowed to connect to this MySQL server

最新推荐文章于 2024-09-23 10:59:02 发布
原创 最新推荐文章于 2024-09-23 10:59:02 发布 · 626 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#MySQL

授权方式解决Host '192.168.1.180' is not allowed to connect to this MySQL server

GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' IDENTIFIED BY 'mypassword' WITH GRANT OPTION
iteye_9680
关注
Mysql远程连接报错：Host is not allowed to connect to this MySQL server
m0_46908220的博客
01-05 1101
最后一步，更新权限。原因：MySQL为设置远程访问权限。第三步、更新用户访问主机数据。在该服务器终端进行更新权限。第一步、登录mysql。
Linux centors7.5 安装MySQL5.7
u012798558的博客
10-12 985
Linux安装64位Mysql5.7 首先下载mysql 地址：https://dev.mysql.com/downloads/mysql/ 下载社区版mysql 下载完成后；ftp上传到服务器 /user/local/目录下，这个自己定！ 使用命令 ，对mysql进行解压缩 [root@instance_4dbde0 local]# tar -zxvf mysql-5.7.20...
Mysql host '192.168.1.1' is not allowed to connect to this mysql server
I need you back to stay
01-27 5471
如何解决： 1。 改表法。 可能是你的帐号不允许从远程登陆，只能在localhost。登录安装的那台电脑，登入mysql后，更改 "mysql" 数据库里的 "user" 表里的 "host" 项，从"localhost"改称"%" mysql>use mysql; mysql>update user set host = '%' where user = 'roo
Host 'ip地址' is not allowed to connect to this MySQL server报错解决方法
仅此而已的日记本
01-11 9370
192.168.1.xxxis not allowed to connect to this mysql server 意思是这个host主机不能访问本机的mysql服务， 需要连接非本机的mysql的时候，默认host是localhost，我们需要将这个mysql连接权限设置成% 更改方法: 在mysql的数据库选择mysql这个数据库，里面有一个user表，进入表中有一个host字段...
解决远程连接阿里云MySQL时3306端口无法访问的问题
铁马秋风大散关
05-29 7499
我在阿里云服务器上安装了MySQL8，但配置远程连接一直不成功。 理论上我只需要修改mysql的user表中root用户的host，然后刷新权限，关闭防火墙即可。 然而。。
Xshell 连接本地的Linux 系统，提示：Could not connect to '192.168.182.128' (port 23): Connection failed
Key_book(句芒安全实验室)
05-05 1058
————————— Xshell 连接本地的Linux 系统，提示：Could not connect to ‘192.168.182.128’ (port 23): Connection failed 解决方法： 1.先检查是否是使用的ssh 连接： 2.输入 ping Linux 的ip 如果是可以ping 通的，说明是网络没有问题，再次进行连接，如果依然是连接失败 3. 先查看防火...
IPV4地址范围
weixin_34405557的博客
07-30 995
实验地址：240.0.0.0 到255.255.255.254 组播地址：224.0.0.0 到 239.255.255.255 主机地址： 0.0.0.0 到 223.255.255.255 私有地址： 10.0.0.0 到 10.255.255.255 (10.0.0.0 /8) 172.16.0.0 到 ...
历史记录 avater 2025-06-20 13:39:25.626 ERROR 5888 — [ main] o.s.boot.SpringApplication : Application run failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘entityManagerFactory’ defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: Invocation of init method failed; nested exception is javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.exception.GenericJDBCException: Unable to open JDBC Connection for DDL execution at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1799) ~[spring-beans-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:594) ~[spring-beans-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:516) ~[spring-beans-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$ doGetBean$ 0(AbstractBeanFactory.java:324) ~[spring-beans-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:322) ~[spring-beans-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1109) ~[spring-context-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:869) ~[spring-context-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:551) ~[spring-context-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:143) ~[spring-boot-2.3.12.RELEASE.jar:2.3.12.RELEASE] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:755) ~[spring-boot-2.3.12.RELEASE.jar:2.3.12.RELEASE] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) ~[spring-boot-2.3.12.RELEASE.jar:2.3.12.RELEASE] at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:402) ~[spring-boot-2.3.12.RELEASE.jar:2.3.12.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:312) ~[spring-boot-2.3.12.RELEASE.jar:2.3.12.RELEASE] at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:173) [spring-boot-2.3.12.RELEASE.jar:2.3.12.RELEASE] at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:153) [spring-boot-2.3.12.RELEASE.jar:2.3.12.RELEASE] at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:95) [spring-boot-2.3.12.RELEASE.jar:2.3.12.RELEASE] at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:172) [spring-web-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5128) [catalina.jar:9.0.37] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [catalina.jar:9.0.37] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:717) [catalina.jar:9.0.37] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690) [catalina.jar:9.0.37] at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705) [catalina.jar:9.0.37] at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1133) [catalina.jar:9.0.37] at org.apache.catalina.startup.HostConfig$ DeployDirectory.run(HostConfig.java:1866) [catalina.jar:9.0.37] at java.util.concurrent.Executors$ RunnableAdapter.call(Executors.java:511) [na:1.8.0_331] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_331] at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) [tomcat-util.jar:9.0.37] at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) [na:1.8.0_331] at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1045) [catalina.jar:9.0.37] at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:429) [catalina.jar:9.0.37] at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1576) [catalina.jar:9.0.37] at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309) [catalina.jar:9.0.37] at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) [catalina.jar:9.0.37] at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423) [catalina.jar:9.0.37] at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366) [catalina.jar:9.0.37] at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:936) [catalina.jar:9.0.37] at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841) [catalina.jar:9.0.37] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [catalina.jar:9.0.37] at org.apache.catalina.core.ContainerBase$ StartChild.call(ContainerBase.java:1384) [catalina.jar:9.0.37] at org.apache.catalina.core.ContainerBase$ StartChild.call(ContainerBase.java:1374) [catalina.jar:9.0.37] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_331] at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) [tomcat-util.jar:9.0.37] at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) [na:1.8.0_331] at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909) [catalina.jar:9.0.37] at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262) [catalina.jar:9.0.37] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [catalina.jar:9.0.37] at org.apache.catalina.core.StandardService.startInternal(StandardService.java:421) [catalina.jar:9.0.37] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [catalina.jar:9.0.37] at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930) [catalina.jar:9.0.37] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [catalina.jar:9.0.37] at org.apache.catalina.startup.Catalina.start(Catalina.java:738) [catalina.jar:9.0.37] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_331] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_331] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_331] at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_331] at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:342) [bootstrap.jar:9.0.37] at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:473) [bootstrap.jar:9.0.37] Caused by: javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory; nested exception is org.hibernate.exception.GenericJDBCException: Unable to open JDBC Connection for DDL execution at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory(AbstractEntityManagerFactoryBean.java:403) ~[spring-orm-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:378) ~[spring-orm-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.afterPropertiesSet(LocalContainerEntityManagerFactoryBean.java:341) ~[spring-orm-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1858) ~[spring-beans-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1795) ~[spring-beans-5.2.15.RELEASE.jar:5.2.15.RELEASE] … 58 common frames omitted Caused by: org.hibernate.exception.GenericJDBCException: Unable to open JDBC Connection for DDL execution at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:47) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:113) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:99) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.resource.transaction.backend.jdbc.internal.DdlTransactionIsolatorNonJtaImpl.getIsolatedConnection(DdlTransactionIsolatorNonJtaImpl.java:69) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.tool.schema.internal.exec.ImprovedExtractionContextImpl.getJdbcConnection(ImprovedExtractionContextImpl.java:60) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.tool.schema.internal.exec.ImprovedExtractionContextImpl.getJdbcDatabaseMetaData(ImprovedExtractionContextImpl.java:67) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.tool.schema.extract.internal.InformationExtractorJdbcDatabaseMetaDataImpl.getTables(InformationExtractorJdbcDatabaseMetaDataImpl.java:333) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.tool.schema.extract.internal.DatabaseInformationImpl.getTablesInformation(DatabaseInformationImpl.java:120) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.tool.schema.internal.GroupedSchemaMigratorImpl.performTablesMigration(GroupedSchemaMigratorImpl.java:65) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.performMigration(AbstractSchemaMigrator.java:207) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.doMigration(AbstractSchemaMigrator.java:114) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:184) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:73) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.internal.SessionFactoryImpl.(SessionFactoryImpl.java:318) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:468) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1259) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider.createContainerEntityManagerFactory(SpringHibernateJpaPersistenceProvider.java:58) ~[spring-orm-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:365) ~[spring-orm-5.2.15.RELEASE.jar:5.2.15.RELEASE] at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory(AbstractEntityManagerFactoryBean.java:391) ~[spring-orm-5.2.15.RELEASE.jar:5.2.15.RELEASE] … 62 common frames omitted Caused by: java.sql.SQLException: null, message from server: “Host ‘WIN-IF8AUPE59UH’ is not allowed to connect to this MySQL server” at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:130) ~[mysql-connector-j-8.0.33.jar:8.0.33] at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) ~[mysql-connector-j-8.0.33.jar:8.0.33] at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:825) ~[mysql-connector-j-8.0.33.jar:8.0.33] at com.mysql.cj.jdbc.ConnectionImpl.(ConnectionImpl.java:446) ~[mysql-connector-j-8.0.33.jar:8.0.33] at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:239) ~[mysql-connector-j-8.0.33.jar:8.0.33] at com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:188) ~[mysql-connector-j-8.0.33.jar:8.0.33] at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:138) ~[HikariCP-3.4.5.jar:na] at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:358) ~[HikariCP-3.4.5.jar:na] at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:206) ~[HikariCP-3.4.5.jar:na] at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:477) ~[HikariCP-3.4.5.jar:na] at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:560) ~[HikariCP-3.4.5.jar:na] at com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:115) ~[HikariCP-3.4.5.jar:na] at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:112) ~[HikariCP-3.4.5.jar:na] at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator$ ConnectionProviderJdbcConnectionAccess.obtainConnection(JdbcEnvironmentInitiator.java:180) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] at org.hibernate.resource.transaction.backend.jdbc.internal.DdlTransactionIsolatorNonJtaImpl.getIsolatedConnection(DdlTransactionIsolatorNonJtaImpl.java:43) ~[hibernate-core-5.4.32.Final.jar:5.4.32.Final] … 77 common frames omitted 链接地址由127.0.0.1改为局域网本地ip地址，还是本机
最新发布
06-21
useSSL=false&serverTimezone=UTCspring.datasource.username=myuserspring.datasource.password=mypassword或者使用IP地址：spring.datasource.url=jdbc:mysql://192.168.x.x:3306/dbname?useSSL=false&serverTime...
zabbix_server.conf 配置文件详解
qq_2331233079的博客
09-08 3146
文章目录一、通用配置二、高级配置三、自定义模块配置 [root@test1 ~]# vim /etc/zabbix/zabbix_server.conf 一、通用配置 ############ GENERAL PARAMETERS ################# ### Option: ListenPort # Listen port for trapper. # # Mandatory: no # Range: 1024-32767 # Default: ListenPort=10051 #
分布式事务之SEATA
Jarvan的博客
08-10 120
需要。
https 出现host name not match 问题
热门推荐
sonycong的专栏
05-26 4万+
'www.xxx.com' does not match the certificate subject provided by the peer 出现这个问题的原因是你访问的域名和你访问服务器的证书的机构(域名)不一致导致的，比如，你的证书是为域名 sss.com注册的，而你访问的时候的域名是xxx.com,这个时候就会报这种错误，解决办法是重写httpclient的HostnameVerif
SSH免密码登录
AZ9009ZA的专栏
12-17 924
一、原理使用公钥登录服务器，而非密码二、使用命令ssh-keygen：生成密钥对(一路回车),执行结果如下：Generating public/private rsa key pair.Enter file in which to save the key (/home/test/.ssh/id_rsa): Created directory '/home/test/.ssh'.Enter passphrase (empty for no passphrase): Enter same passphrase
MySQL Authentication to host for user using method 'mysql_native_password' failed
Gavin luo 我们共同努力
04-03 6008
最近项目一直在遇到这个错误，之前也偶尔遇到，了解可能跟CPU使用率高有关， 但也不清楚具体为什么，借这次机会刚好研究一下 首先还是感谢大牛在这篇文章给予的提示https://www.linuxidc.com/Linux/2018-12/156001.htm 首先我的MySql.Data 版本也是6.9.9 的， 相信这个版本下的都会有这个问题 文章上说是读取系统信息超时引起的。 看了代码的确有读系...
MySQL 访问权限 系统 说明
David Dai -- Focus on Oracle
12-01 1万+
The primaryfunction of the MySQL privilege system is to authenticate a user who connectsfrom a given host and to associate that user with privileges on a database suchas SELECT, INSERT, UPDATE, and DE
自启动脚本中基于dropbear的免密scp无法生效的解决措施
06-28 835
最近写了一个自动上传日志文件的脚本放在现场设备中，使用免密码的scp的上传日志到服务器，该设备的ssh是基于dropbear实现。脚本放到设备中测试，发现在在命令行模式下启动脚本，可以自动上传日志，但把脚本设置成开机自启动后，scp却无法运行。原来dropbear默认的home目录是 /. ，但实际上是 /root，所以需要设置 $HOME 环境变量。查阅日志发现在自启动脚本中scp执行时，报“Host 'reboot重启设备，发现脚本中的scp可正常执行了，日志可自动上传啦！
连接MySQL提示1130 -Host ‘192.168.10.1‘is not allowed to connect to this MySQL server
weixin_63933547的博客
09-23 710
问题原因：是因为192.168.10.1服务器不允许连接特定的服务器ip
‘Host’ is not allowed to connect to this mysql server
qq_37752382的博客
10-16 176
‘Host’ is not allowed to connect to this mysql server 不允许“主机”连接到此MyS QL服务器 1、进入mysql数据库，选择mysql 2、更新 user表的host, select * from user update user set host = '%' where user='root' 3、重启服务(cmd命令框)...
IDEA DataGrip连接sqlserver 提示驱动程序无法通过使用安全套接字层(SSL)加密与 SQL Server 建立安全连接的解决方法
qq_53058639的博客
02-23 1735
从时代发展的角度看，网络安全的知识是学不完的，而且以后要学的会更多，同学们要摆正心态，既然选择入门网络安全，就不能仅仅只是入门程度而已，能力越强机会才越多。因为入门学习阶段知识点比较杂，所以我讲得比较笼统，大家如果有不懂的地方可以找我咨询，我保证知无不言言无不尽，需要相关资料也可以找我要，我的网盘里一大堆资料都在吃灰呢。干货主要有：①1000+CTF历届题库（主流和经典的应该都有了）②CTF技术文档（最全中文版）③项目源码（四五十个有趣且经典的练手项目及源码）
解决报错ssh: connect to host 192.168.76.128 port 22: Connection refused
我的个人博客
10-14 4828
Windows用ssh命令远程登录Ubuntu、macOS，解决报错ssh: connect to host 192.168.76.128 port 22: Connection refused
Host '192.168.1.199' is not allowed to connect to this MySQL server
03-30
### 解决 MySQL 错误 “Host is not allowed to connect”的方法 当遇到错误消息 `Host '192.168.1.199' is not allowed to connect` 时，这通常是因为 MySQL 用户权限配置不正确，或者未允许特定 IP 地址访问数据库。以下是详细的解决方案： #### 1. 检查并修改 MySQL 用户权限 可以通过以下 SQL 命令来授予指定主机的访问权限： ```sql GRANT ALL PRIVILEGES ON *.* TO 'your_username'@'192.168.1.199' IDENTIFIED BY 'your_password'; FLUSH PRIVILEGES; ``` 上述命令的作用是赋予用户 `'your_username'` 来自 IP 地址 `192.168.1.199` 的完全访问权限[^3]。 如果希望该用户可以从任何远程地址连接，则可以使用通配符 `%` 替代具体的 IP 地址： ```sql GRANT ALL PRIVILEGES ON *.* TO 'your_username'@'%' IDENTIFIED BY 'your_password'; FLUSH PRIVILEGES; ``` #### 2. 配置 MySQL 绑定地址 默认情况下，MySQL 可能仅绑定到本地回环接口 (localhost 或 127.0.0.1)，从而阻止外部客户端连接。需要编辑 MySQL 配置文件 `/etc/mysql/my.cnf` 或 `/etc/my.cnf` 并找到如下行： ```ini bind-address = 127.0.0.1 ``` 将其更改为服务器的实际 IP 地址或设置为 `0.0.0.0`（表示监听所有网络接口）： ```ini bind-address = 0.0.0.0 ``` 保存更改后重启 MySQL 服务以使新配置生效： ```bash sudo systemctl restart mysql ``` #### 3. 确认防火墙规则 确保服务器上的防火墙不会阻止来自目标 IP (`192.168.1.199`) 对 MySQL 默认端口 (3306) 的访问。可以在 Linux 上运行以下命令打开相应端口： ```bash sudo ufw allow 3306/tcp ``` 对于其他操作系统，请查阅其对应的防火墙管理文档。 #### 4. 测试连接状态 完成以上操作之后，尝试重新建立与 MySQL 数据库之间的连接，并通过调用函数验证是否存在新的异常情况： ```php $mysqli = new mysqli('192.168.1.199', 'your_username', 'your_password', 'test_db'); if ($mysqli->connect_error) { echo "Error: " . $mysqli->connect_error; } else { echo "Connection successful!"; } ``` 此脚本会显示具体失败原因以便进一步排查问题所在[^4]。 ---
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值