发表新帖
发表新帖

nacos2.4.3版本配置鉴权之后注册不上nacos

Blade 未结
关注 举报
2 994
颜丙
颜丙 剑者 2024-11-14 08:09

一、该问题的重现步骤是什么？

  1. 使用nacos版本为2.4.3，并且application.properties配置如图

    image.png

    已经确定账号密码可以直接登入进入nacos

    image.png


2. 修改Bladex3.2.0.REALSE版本一下几个文件

DynamicRouteServiceListener.java

image.png

LauncherConstant.java

image.png

image.png

LauncherServiceImpl.java

image.png

3.结果运行报错，注册不上nacos

image.png

2024-11-14 08:06:15.379 ERROR 18108 --- [           main] c.a.c.n.registry.NacosServiceRegistry    : nacos registry, blade-gateway register failed...NacosRegistration{nacosDiscoveryProperties=NacosDiscoveryProperties{serverAddr='192.168.10.131:8848', username='nacos', password='nacos_ybzPROD129!@(', endpoint='', namespace='', watchDelay=30000, logName='', service='blade-gateway', weight=1.0, clusterName='DEFAULT', group='DEFAULT_GROUP', namingLoadCacheAtStart='false', metadata={IPv6=[2001:0:2851:b9f0:20aa:c4d4:8d1c:40a9], preserved.register.source=SPRING_CLOUD}, registerEnabled=true, ip='192.168.2.138', networkInterface='', port=80, secure=false, accessKey='', secretKey='', heartBeatInterval=null, heartBeatTimeout=null, ipDeleteTimeout=null, instanceEnabled=true, ephemeral=true, failureToleranceEnabled=false}, ipDeleteTimeout=null, failFast=true}},


com.alibaba.nacos.api.exception.NacosException: Client not connected, current status:STARTING

at com.alibaba.nacos.common.remote.client.RpcClient.request(RpcClient.java:639) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.nacos.common.remote.client.RpcClient.request(RpcClient.java:619) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.nacos.client.naming.remote.gprc.NamingGrpcClientProxy.requestToServer(NamingGrpcClientProxy.java:304) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.nacos.client.naming.remote.gprc.NamingGrpcClientProxy.doRegisterService(NamingGrpcClientProxy.java:154) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.nacos.client.naming.remote.gprc.NamingGrpcClientProxy.registerService(NamingGrpcClientProxy.java:117) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.nacos.client.naming.remote.NamingClientProxyDelegate.registerService(NamingClientProxyDelegate.java:96) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.nacos.client.naming.NacosNamingService.registerInstance(NacosNamingService.java:149) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.cloud.nacos.registry.NacosServiceRegistry.register(NacosServiceRegistry.java:75) ~[spring-cloud-starter-alibaba-nacos-discovery-2021.0.5.0.jar:2021.0.5.0]

at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.register(AbstractAutoServiceRegistration.java:232) [spring-cloud-commons-3.1.7.jar:3.1.7]

at com.alibaba.cloud.nacos.registry.NacosAutoServiceRegistration.register(NacosAutoServiceRegistration.java:78) [spring-cloud-starter-alibaba-nacos-discovery-2021.0.5.0.jar:2021.0.5.0]

at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.start(AbstractAutoServiceRegistration.java:133) [spring-cloud-commons-3.1.7.jar:3.1.7]

at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.bind(AbstractAutoServiceRegistration.java:98) [spring-cloud-commons-3.1.7.jar:3.1.7]

at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.onApplicationEvent(AbstractAutoServiceRegistration.java:86) [spring-cloud-commons-3.1.7.jar:3.1.7]

at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.onApplicationEvent(AbstractAutoServiceRegistration.java:47) [spring-cloud-commons-3.1.7.jar:3.1.7]

at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176) [spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169) [spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143) [spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:421) [spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:378) [spring-context-5.3.29.jar:5.3.29]

at org.springframework.boot.web.reactive.context.WebServerManager.start(WebServerManager.java:57) [spring-boot-2.7.15.jar:2.7.15]

at org.springframework.boot.web.reactive.context.WebServerStartStopLifecycle.start(WebServerStartStopLifecycle.java:40) [spring-boot-2.7.15.jar:2.7.15]

at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:179) [spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:54) [spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:357) [spring-context-5.3.29.jar:5.3.29]

at java.lang.Iterable.forEach(Iterable.java:75) ~[na:1.8.0_402]

at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:156) [spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:124) [spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:938) [spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586) [spring-context-5.3.29.jar:5.3.29]

at org.springframework.boot.web.reactive.context.ReactiveWebServerApplicationContext.refresh(ReactiveWebServerApplicationContext.java:66) ~[spring-boot-2.7.15.jar:2.7.15]

at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:731) ~[spring-boot-2.7.15.jar:2.7.15]

at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:408) ~[spring-boot-2.7.15.jar:2.7.15]

at org.springframework.boot.SpringApplication.run(SpringApplication.java:307) ~[spring-boot-2.7.15.jar:2.7.15]

at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:164) ~[spring-boot-2.7.15.jar:2.7.15]

at org.springblade.core.launch.BladeApplication.run(BladeApplication.java:50) ~[blade-core-launch-3.2.0.RELEASE.jar:na]

at org.springblade.gateway.GateWayApplication.main(GateWayApplication.java:36) ~[classes/:na]


2024-11-14 08:06:15.380  WARN 18108 --- [           main] onfigReactiveWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Failed to start bean 'webServerStartStop'; nested exception is java.lang.reflect.UndeclaredThrowableException

2024-11-14 08:06:17.866  INFO 18108 --- [           main] ConditionEvaluationReportLoggingListener : 


Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.

2024-11-14 08:06:17.916 ERROR 18108 --- [           main] o.s.boot.SpringApplication               : Application run failed


org.springframework.context.ApplicationContextException: Failed to start bean 'webServerStartStop'; nested exception is java.lang.reflect.UndeclaredThrowableException

at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182) ~[spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:54) ~[spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:357) ~[spring-context-5.3.29.jar:5.3.29]

at java.lang.Iterable.forEach(Iterable.java:75) ~[na:1.8.0_402]

at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:156) ~[spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:124) ~[spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:938) ~[spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586) ~[spring-context-5.3.29.jar:5.3.29]

at org.springframework.boot.web.reactive.context.ReactiveWebServerApplicationContext.refresh(ReactiveWebServerApplicationContext.java:66) ~[spring-boot-2.7.15.jar:2.7.15]

at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:731) ~[spring-boot-2.7.15.jar:2.7.15]

at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:408) ~[spring-boot-2.7.15.jar:2.7.15]

at org.springframework.boot.SpringApplication.run(SpringApplication.java:307) ~[spring-boot-2.7.15.jar:2.7.15]

at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:164) [spring-boot-2.7.15.jar:2.7.15]

at org.springblade.core.launch.BladeApplication.run(BladeApplication.java:50) [blade-core-launch-3.2.0.RELEASE.jar:na]

at org.springblade.gateway.GateWayApplication.main(GateWayApplication.java:36) [classes/:na]

Caused by: java.lang.reflect.UndeclaredThrowableException: null

at org.springframework.util.ReflectionUtils.rethrowRuntimeException(ReflectionUtils.java:147) ~[spring-core-5.3.29.jar:5.3.29]

at com.alibaba.cloud.nacos.registry.NacosServiceRegistry.register(NacosServiceRegistry.java:83) ~[spring-cloud-starter-alibaba-nacos-discovery-2021.0.5.0.jar:2021.0.5.0]

at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.register(AbstractAutoServiceRegistration.java:232) ~[spring-cloud-commons-3.1.7.jar:3.1.7]

at com.alibaba.cloud.nacos.registry.NacosAutoServiceRegistration.register(NacosAutoServiceRegistration.java:78) ~[spring-cloud-starter-alibaba-nacos-discovery-2021.0.5.0.jar:2021.0.5.0]

at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.start(AbstractAutoServiceRegistration.java:133) ~[spring-cloud-commons-3.1.7.jar:3.1.7]

at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.bind(AbstractAutoServiceRegistration.java:98) ~[spring-cloud-commons-3.1.7.jar:3.1.7]

at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.onApplicationEvent(AbstractAutoServiceRegistration.java:86) ~[spring-cloud-commons-3.1.7.jar:3.1.7]

at org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.onApplicationEvent(AbstractAutoServiceRegistration.java:47) ~[spring-cloud-commons-3.1.7.jar:3.1.7]

at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176) ~[spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169) ~[spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143) ~[spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:421) ~[spring-context-5.3.29.jar:5.3.29]

at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:378) ~[spring-context-5.3.29.jar:5.3.29]

at org.springframework.boot.web.reactive.context.WebServerManager.start(WebServerManager.java:57) ~[spring-boot-2.7.15.jar:2.7.15]

at org.springframework.boot.web.reactive.context.WebServerStartStopLifecycle.start(WebServerStartStopLifecycle.java:40) ~[spring-boot-2.7.15.jar:2.7.15]

at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:179) ~[spring-context-5.3.29.jar:5.3.29]

... 14 common frames omitted

Caused by: com.alibaba.nacos.api.exception.NacosException: Client not connected, current status:STARTING

at com.alibaba.nacos.common.remote.client.RpcClient.request(RpcClient.java:639) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.nacos.common.remote.client.RpcClient.request(RpcClient.java:619) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.nacos.client.naming.remote.gprc.NamingGrpcClientProxy.requestToServer(NamingGrpcClientProxy.java:304) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.nacos.client.naming.remote.gprc.NamingGrpcClientProxy.doRegisterService(NamingGrpcClientProxy.java:154) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.nacos.client.naming.remote.gprc.NamingGrpcClientProxy.registerService(NamingGrpcClientProxy.java:117) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.nacos.client.naming.remote.NamingClientProxyDelegate.registerService(NamingClientProxyDelegate.java:96) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.nacos.client.naming.NacosNamingService.registerInstance(NacosNamingService.java:149) ~[nacos-client-2.1.2.jar:na]

at com.alibaba.cloud.nacos.registry.NacosServiceRegistry.register(NacosServiceRegistry.java:75) ~[spring-cloud-starter-alibaba-nacos-discovery-2021.0.5.0.jar:2021.0.5.0]

... 28 common frames omitted


2024-11-14 08:06:18.849  WARN 18108 --- [       Thread-3] c.a.n.common.http.HttpClientBeanHolder   : [HttpClientBeanHolder] Start destroying common HttpClient

2024-11-14 08:06:18.850  WARN 18108 --- [      Thread-10] c.a.nacos.common.notify.NotifyCenter     : [NotifyCenter] Start destroying Publisher

2024-11-14 08:06:18.850  WARN 18108 --- [      Thread-10] c.a.nacos.common.notify.NotifyCenter     : [NotifyCenter] Destruction of the end

Disconnected from the target VM, address: '127.0.0.1:60128', transport: 'socket'


二、你期待的结果是什么？实际看到的又是什么？


三、你正在使用的是什么产品，什么版本？在什么操作系统上？

BALDEX3.2.REALSE,程序在win11环境上跑，nacos在centos7.9的操作系统上运行

四、请提供详细的错误堆栈信息，这很重要。


五、若有更多详细信息，请在下面提供。

2条回答
  • admin - BladeX作者
    2024-11-14 09:03

    nacos client的依赖有没有升级到2.4.3

    作者追问:2024-11-14 09:37

    image.png

    升级之后还是不行，同样注册不上nacos

    作者追问:2024-11-14 11:16

    image.png


    最新版本也不行，博主能给一个行的2.4.3的nacos嘛

    作者追问:2024-11-14 11:21

    image.png


    开放了9948和8848和9949 的端口，然后出现这个错误了，好像是连接上了，这里访问是怎么个事儿

    回答: 2024-11-14 12:32

    既然花了这么久的时间都跑不起来而其他人都能跑，那就是你环境问题，就应该尽可能减少所有影响因素和条件。

    你直接在本地跑nacos服务，账号名密码也别改就默认nacos、nacos，看看是否能跑起来。本地默认配置跑起来了，你再尝试去修改其他的配置，再去部署到服务器远程连接。这个帖子的注意点再过一遍：https://sns.bladex.cn/q-41.html

    本地docker命令如下：

    		docker run \
    		  --name nacos-standalone -d -p 8848:8848 -p 9848:9848 -p 9849:9849 \
    		  -e NACOS_AUTH_ENABLE=true \
    		  -e MODE=standalone \
    		  -e NACOS_AUTH_TOKEN=改成你定义的token值 \
    		  -e NACOS_AUTH_IDENTITY_KEY=nacos \
    		  -e NACOS_AUTH_IDENTITY_VALUE=nacos \
    		  -e NACOS_AUTH_CACHE_ENABLE=true \
    		  nacos/nacos-server:v2.4.3


    0 讨论(0)
  • 颜丙
    2024-11-14 09:20

    如何升级到2.4.3

    作者追问:2024-11-14 09:24

    bladex根目录的pom.xml对应位置加入nacos-client的依赖，指定2.4.3

    IMG_3705.jpeg

    回答: 2024-11-14 09:31

    image.png


    升级之后还是不行

    回答: 2024-11-14 09:35

    image.png

    升级之后还是不行。同样的错误注册不上

    作者追问:2024-11-14 10:27

    你用最新版的bladex配置试试看，最新版如下图。用最新版可以先排除你自己配置上的问题，来看看是不是nacos的部署问题

    CleanShot20241114102507@2x.png

    作者追问:2024-11-14 11:06

    另外如果你nacos不是本机部署，需要开通8848\9848\9849三个端口才可以远程连接访问

    0 讨论(0)
代码语言
 看不清?
提交回复
官方产品
BladeX 企业级开发平台 BladeX 可视化数据大屏
官方新品
BladeX 大模型开发平台 BladeX 物联网开发平台
热议问题
/blade-auth/oauth/token 获取token接口报请求头中未找到 [Authorization] 信息 1
树形的模型搜索有bug 1
BladeX-Tool 的JDK8版本的版本有吗？目前只看到17的版本 1
前端Saber3升级无法启动 2
bladex的登陆验证码如何配置清晰度？ 1
物联网平台（cloud版）blade-emqx部署后出现拒绝连接：未经授权 1
物联系统升级集成企业系统 1
物联系统运行报运行错误 2
表格树updateKeyChildren，是否可用，怎么没有demo 1
mqqt数据绑定方式，无法加载数据 2
layui

扫一扫访问 Blade技术社区 移动端

Blade技术社区 2025 © 上海布雷德科技有限公司 沪ICP备2023009528号-1 苏公网安备 32041102000998号