Skip to content
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

添加自定义健康检查地址时:403 resource name invalid! #3005

Closed
xingwl2018 opened this issue Jun 9, 2020 · 2 comments
Closed
Assignees
Labels
area/Naming kind/bug Category issues or prs related to bug.
Milestone

Comments

@xingwl2018
Copy link

Issue Description

Type: bug report or feature request

Describe what happened (or what feature you want)

添加异常:

error: "Forbidden"
message: "resource name invalid!"
path: "/nacos/v1/ns/cluster"
status: 403
timestamp: "2020-06-09T10:27:45.536+0000"

Describe what you expected to happen

request url : ip:port/nacos/v1/ns/cluster?&accessToken=xxx

How to reproduce it (as minimally and precisely as possible)

Tell us your environment

nacos-server 1.3.0

Anything else we need to know?

image

@KomachiSion KomachiSion added kind/bug Category issues or prs related to bug. area/Naming labels Jun 9, 2020
@KomachiSion KomachiSion added this to the 1.3.1 milestone Jun 9, 2020
@KomachiSion KomachiSion added kind/bug Category issues or prs related to bug. area/Naming and removed area/Naming kind/bug Category issues or prs related to bug. labels Jun 9, 2020
@KomachiSion
Copy link
Collaborator

KomachiSion commented Jun 9, 2020

Please close the auth and retry, I will try to find out and fix this problem.

@KomachiSion KomachiSion self-assigned this Jun 9, 2020
@xingwl2018
Copy link
Author

image
After the authentication is turned off, it can be added successfully. However, if the port is not assigned correctly, it is still port 80. And it seems that the health examination method will not take effect after it is modified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/Naming kind/bug Category issues or prs related to bug.
Projects
None yet
Development

No branches or pull requests

3 participants