PMM2 client not registering

Percona Monitoring and Management (PMM) PMM 2.x
1

I have been following the process of installing the PMM2 server and client from:
[url]https://www.percona.com/blog/2019/09/19/installing-percona-monitoring-and-management-pmm-2-for-the-first-time/[/url]

and get to the very last point of registering the client on the server and it doesn’t work. It responds with:


Checking local pmm-agent status...
pmm-agent is running.
Registering pmm-agent on PMM Server...
Failed to register pmm-agent on PMM Server: Post https://admin:3/v1/management/Node/Register: dial tcp: lookup admin on ***.***.***.***: no such host.

Two things are strange here - the IP address shown in the error is not the IP address of the server or the one listed in the --server-url (odd) and also when I put the incorrect password in, it fails due to:

Failed to register pmm-agent on PMM Server: Invalid username or password.

Any advice would be greatly appreciated…

Thank you

2

Are you using httpS for your PMM Server?

3

Yes - https://...:443

4

Depending on what username/password are, you may have to URL encode them in order to register the client with the PMM server.

As you probably know, special characters take different form in URLs - and you’re using an URL to register. E.g. if the password you’re using is: P@$$w0rd, the URL encoded form
would be P%40%24%24w0rd

1 Like
5

Genius! Thank you!!!

6

hi ,

getting below error for pmm-client->
Failed to register pmm-agent on PMM Server: Post “https://ip_address:80/v1/management/nodes”: http: server gave HTTP response to HTTPS client.
time=“2025-03-31T09:59:51.669+00:00” level=info msg=“‘pmm-agent setup’ exited with 1” component=entrypoint

i dont have SSL. so i dont want to use https.

7

hi @Amol_Nagotkar_Helo.a

I would suggest you to use https and 443 port on PMM but with insecure-tis option. In this case PMM server will have its SSL, but will not force clients to use it.

For example it’s my case for sandbox environment where we don’t want to use SSL. --server-insecure-tls flag helps alot.

pmm-admin config 1.2.3.4 generic NODE_NAME --server-insecure-tls --server url=https:/pmm_admin_user:pmm_admin_pwd@pmm.domain.com/ --force