-
Notifications
You must be signed in to change notification settings - Fork 381
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
dependency failed to start: container higress-controller-1 is unhealthy Starting Higress fails with 1 #658
Comments
Could you execute the following command in the installation folder and post its output?
./bin/logs.sh controller
|
higress-controller-1 | 2023-11-29T08:43:27.700625Z info FLAG: --clusterAliases="[]" |
Then exec |
higress-apiserver-1 | W1129 09:56:00.733692 1 authorization.go:54] Authorization is disabled |
Nacos server is ready |
So you use nacos:/192.168.6.205:30848 as the nacos server URL, and 192.168.6.205 is a LB or reverse proxy, not the nacos server itself, right? You need to expose the 9848 port of nacos server(s) on 192.168.6.205:31848 as well. For a detailed reason, you can refer to this doc: https://nacos.io/en-us/docs/v2/upgrading/2.0.0-compatibility.html |
非常感谢,正如您所说的,我确实是使用了错误的IP,现在已经好了。 |
dependency failed to start: container higress-controller-1 is unhealthy
Starting Higress fails with 1
The text was updated successfully, but these errors were encountered: