-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client not connected, current status:STARTING #3736
Comments
Why do I configure the public ip address :8848, but the error message is 127.0.0.1:8848? |
if use docker container, pls mapping 9848 port. try again |
Can you provide a simple demo? |
The gateway connects to the nacos demo |
This is a network issue between the containers, you can check if the nacos container and the gateway container can communicate properly. |
ThenThen should I use the container name yunnian-nacos:8848? I've tried this before. No. |
a simple way, you can run |
Hello, I configured server-addr: 8.136.114.59:8848 in bootstrap.yml. Why is the value 127.0.0.1:8848 when I start the connection? |
Thank you for your patient answer. I can connect to nacos by running gateway locally. My local debug breakpoint read nacos source code configuration and loaded my configuration 8.136.114.59:8848, but the online environment, as you see, reported an error. I see the environmental error on the line: NacosRegistration{nacosDiscoveryProperties=NacosDiscoveryProperties{serverAddr='127.0.0.1:8848', The Client is not connected and current status:STARTING. Why is it 127.0.0.1:8848? I checked the configuration file and there are no configuration errors. Can you give me some ideas for troubleshooting? |
Is the online environment configured the same way? dev config file |
Yes, the environment is the same online |
imo, In an online environment, it is possible that the dev configuration file is not loaded correctly, but instead, a default is loaded, which you can see more about in the logs Looking at the online environment |
if is |
My environment here is dev |
Make sure your config file is loaded correctly, or is it present in the container? It looks like the config file is loaded correctly |
Now I can not locate what is the problem, this problem makes me confused, no idea |
Hello, thank you very much! I've solved my problem。 |
Good job, config file not load or network question. |
Which Component
use pring-cloud-alibaba
Startup error
Screenshots
If applicable, add screenshots to help explain your problem.
Startup error:
docker-compose:
springboot nacos yml :
aliyun The security group has been released
Additional context
Add any other context about the problem here.
<spring-boot.version>2.7.13</spring-boot.version>
<spring-cloud.version>2021.0.8</spring-cloud.version>
<spring-cloud-alibaba.version>2021.0.5.0</spring-cloud-alibaba.version>
The text was updated successfully, but these errors were encountered: