K7

K7Blog

须知少年凌云志 曾许人间第一流.
proton
telegram
Home文章归档

Nezha Probe Installation Tutorial and Solution to Installation Issues in China

#哪吒探针#哪吒监控#vps监控1144
AI Translation
This post is translated from Chinese into English through AI.View Original
AI-generated summary
The writer used to buy multiple small servers to distribute the risk and took advantage of discounts on annual payment plans. They recently installed a monitoring tool called Nezha on their servers and are happy with the results. They provide a detailed guide on setting up the Nezha monitoring tool on both the panel and monitoring servers, including creating a GitHub OAuth app and setting up reverse proxies. They also explain how to install the Nezha agent on Windows and Linux servers. If users in China face issues with the official installation script, they provide manual installation instructions.

Due to my previous belief in not putting all my eggs in one basket, and the fact that it was more cost-effective for merchants to sell some annual payment machines, I kept buying chicks and had up to twenty machines with different performance. In the past, I basically didn't give the chicks any injections, and I was too lazy to aggregate them together for management even if I had a dozen or so in my hand. I didn't think it was of much use, at most, I would run a program on this server and hang a domain name, and set up monitoring alarms.

Now I still have a dozen or so chicks, and recently I have installed the Nezha probe, which feels inexplicably cool.

Snipaste_2024-04-07_09-02-38

Last year, I bought a few junk chicks from CLOUDCONE, and they automatically deducted my credit card at the beginning of this year. Since it was an annual fee, I had to use them, but fortunately, I am now making use of them.

The online time is relatively new, and I like to reinstall the system before using it.

Setup Tutorial:#

Nezha Probe Official Documentation: https://nezha.wiki/

GitHub: https://github.com/naiba/nezha

Prepare a VPS chick as the panel end, and prepare several VPS chicks as monitoring ends.

Parse two domain names to the panel end, one can be used as the panel end access with CDN, and the other cannot be used as the communication end (using the server IP is also possible). The CDN needs to support the WebSocket protocol.

Prepare nginx reverse proxy for domain name access, and it is also possible to use Baota panel as a reverse proxy.

Setting up the panel end#

Get the Client ID and Secret from GitHub

Because Nezha Monitor integrates with GitHub, Gitlab, and Gitee as backend administrator accounts, we need to create a third-party login application.

Here we use GitHub as an example (first open the GitHub page to log in):

Then open: https://github.com/settings/developers and select "OAuth Apps" - "New OAuth App" in order.

2024040403125724

Application name - Fill in randomly
Homepage URL - Fill in the access domain name of the panel

For example: "http://cdn.example.com" (your domain name)
Authorization callback URL - Fill in the callback address

For example: "http://cdn.example.com/oauth2/callback" (don't forget /oauth2/callback)

2024040403132190

Click "Register application"

Save the Client ID on the page, and then click "Generate a new client secret" to create a new Client Secret. The newly created secret will only be displayed once, so please keep it safe. Please refer to the following figure:

2024040403140181

Install the panel end on the server#

On the panel server, run the installation script:

curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh

If your panel server is located in mainland China, you can use the mirror:

curl -L https://gitee.com/naibahq/nezha/raw/master/script/install.sh -o nezha.sh && chmod +x nezha.sh && sudo CN=true ./nezha.sh

  • After Docker is installed, enter the following values:

  • OAuth provider - choose one from GitHub, Gitlab, and Gitee

  • Client ID - the previously saved Client ID

  • Client Secret - the previously saved secret

  • Username - the username in the OAuth provider

  • Site title - custom site title

  • Access port - public access port, customizable, default is 8008

  • Agent communication port - the communication port between Agent and Dashboard, default is 5555

  • After entering the values, wait for the image to be pulled

  • After the installation is complete, if everything is normal, you can access the panel by using the domain name + port number, such as "http://cdn.example.com:8008"

  • If you need to run the script again in the future, you can run:

./nezha.sh

to open the management script.

Configure reverse proxy

Create a new site in the Baota panel, fill in the domain name for public access, such as "http://cdn.example.com", and then click "Settings" to enter the site settings options, select "Reverse Proxy" - "New Reverse Proxy"

Customize a proxy name, fill in http://127.0.0.1 in the "Target URL" below, and then click "Save"

Open the configuration file on the right side of the newly created reverse proxy, and replace the configuration file with the following content:

#PROXY-START/
location / {
    proxy_pass http://127.0.0.1:8008;
    proxy_set_header Host $http_host;
    proxy_set_header      Upgrade $http_upgrade;
}
location ~ ^/(ws|terminal/.+)$  {
    proxy_pass http://127.0.0.1:8008;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $http_host;
}
#PROXY-END/

Click "Save" and now you should be able to access the panel directly using the domain name, such as: "http://cdn.example.com".

Setting up the monitoring end#

Currently, Nezha Monitor supports one-click installation of the Agent on Windows and Linux, making it easy to deploy on servers.

Preparation#

You need to set up the communication domain name in the management panel in advance. This domain name cannot be connected to CDN. Here, we use the example communication domain name "data.example.com" for demonstration purposes.
Go to the "Settings" page in the backend management panel and fill in the communication domain name in the "Panel server domain name/IP not connected to CDN" field, and then click "Save".

One-click installation in Linux (Ubuntu, Debian, CentOS)#

First, add a server in the management panel

Click the green Linux icon button next to the newly added server, and copy the one-click installation command

Run the copied one-click installation command on the controlled server, and wait for the installation to complete, then return to the Dashboard homepage to see if the server is online.

One-click installation in Windows#

First, add a server in the management panel

Click the green Windows icon button next to the newly added server, and copy the one-click installation command

Enter the Windows server and run PowerShell. In PowerShell, run the copied installation command

If prompted to confirm "Change execution policy", select Y

Wait for the installation to complete, then return to the Dashboard homepage to see if the server is online

Installing the Agent (monitoring end) in other ways#

Install on Linux

First, add a server in the management panel

On the controlled server, run the script (for servers located in mainland China, please use the mirror):

curl -L https://raw.githubusercontent.com/naiba/nezha/master/script/install.sh  -o nezha.sh && chmod +x nezha.sh && sudo ./nezha.sh

If your controlled server is located in mainland China, you can use the mirror:

curl -L https://gitee.com/naibahq/nezha/raw/master/script/install.sh -o nezha.sh && chmod +x nezha.sh && sudo CN=true ./nezha.sh
  • Select "Install monitoring Agent"
  • Enter the communication domain name, such as: "data.example.com"
  • Enter the panel communication port (gRPC port), default is 5555
  • Enter the Agent key, the Agent key is generated when adding a server in the management panel, and can be found on the "Servers" page in the management panel
  • Wait for the installation to complete, then return to the Dashboard homepage to see if the server is online

Manual installation in Windows#

Please refer to the community article: Nezha Probe - Windows Client Installation

Unable to install the monitoring end in China#

If you use the official mirror script to install, you may encounter the same situation as me:

Snipaste_2024-04-07_08-38-10


Snipaste_2024-04-07_08-38-28

The following content is from nezha.sh

NZ_BASE_PATH="/opt/nezha"
NZ_AGENT_PATH="${NZ_BASE_PATH}/agent"
NZ_AGENT_SERVICE="/etc/systemd/system/nezha-agent.service"
  1. "/opt/nezha" is the storage directory for the core of the panel, including Dashboard and Agent
  2. "/opt/nezha/agent" combined with the above, this directory is the storage location of the core files of the proxy end
  3. "/etc/systemd/system/nezha-agent.service"
  4. For small partners who are familiar with the Liunx system, they will know that this file determines the startup of the Nezha proxy end

Steps#

Please download nezha-agent from https://api.github.com/repos/nezhahq/agent/releases/latest, choose the compressed package of your system version, and extract it locally. There will be a binary file.

Create the "/opt/nezha/agent" directory on the server, put nezha-agent in it, and then execute:

chmod +x nezha-agent

Create a nezha-agent.service file in the "/etc/systemd/system/" directory, replace the code below, and save it:

[Unit]
Description=Nezha Agent
After=syslog.target
#After=network.target
#After=nezha-dashboard.service

[Service]
# Modify these two values and uncomment them if you have
# repos with lots of files and get an HTTP error 500 because
# of that
###
#LimitMEMLOCK=infinity
#LimitNOFILE=65535
Type=simple
User=root
Group=root
WorkingDirectory=/opt/nezha/agent/
ExecStart=/opt/nezha/agent/nezha-agent -s 1.1.1.1:5555 -p 密钥
Restart=always
#Environment=DEBUG=true

# Some distributions may not support these hardening directives. If you cannot start the service due
# to an unknown option, comment out the ones not supported by your version of systemd.
#ProtectSystem=full
#PrivateDevices=yes
#PrivateTmp=yes
#NoNewPrivileges=true

[Install]
WantedBy=multi-user.target

Replace 1.1.1.1:5555 and 密钥 with your own, and finally execute the following command:

systemctl daemon-reload
systemctl enable nezha-agent
systemctl restart nezha-agent

Finally, refresh the Nezha Probe backend to see the chick online.

Loading...
Ownership of this post data is guaranteed by blockchain and smart contracts to the creator alone.