-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
why i can't bind my service? #899
Comments
What do you mean by 'binding'? |
"Bind" is just a habitual way of saying it.... Sorry for the misunderstanding, what I meant was "(used for) nezha-agent installation command (to bind the server)" I have used the installation command on the server, but it didn't work, and then an error pop-up window popped up (see the picture below) |
Normally the installation command will install nezha-agent on your system. |
The above is the information provided by my server. During this process, I also found a new problem, that is, the nezha-dashboard installed in docker cannot be detected normally. There is no valuable information in the log, and everything runs according to the script during the execution process. The problem is unlikely to occur in my own deployment problem or network error. But I still cannot use nezha-agent by installing the command. There is no server with nezha-agent installed on the dash master. |
Update to the latest version of script which fixed the Docker image detection. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
提供你的配置文件内容 |
强制刷新就会没有这个错误了 |
Environment
Debian GNU/Linux 12 (bookworm) x86_64
Nezha Version
Nezha 1.3.0
Describe the bug
To Reproduce
Additional Context
Validation
The text was updated successfully, but these errors were encountered: