# Invalid username or password **URL:** \ **Category:** PMM 3.x\ **Tags:** pmm\ **Created:** [October 30, 2025, 8:34am UTC](https://forums.percona.com/t/invalid-username-or-password/39656 "2025-10-30T08:34:03Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![khaled1](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@khaled1](https://forums.percona.com/u/khaled1)\ **Post date:** [October 30, 2025, 8:34am UTC](https://forums.percona.com/t/invalid-username-or-password/39656/1 "2025-10-30T08:34:04Z")
I Installed Percona PMM 3 on Debian 13 from below script and the setup was completed successfully but after the setup I cannot login with error invalid username or password then I see that Debian 13 is not fully supported, the I reinstalled it on Debian 12 and I faced the same problem, I used this script curl -fsSL [https://www.percona.com/get/pmm](https://www.percona.com/get/pmm) | /bin/bash what is the problem and how can I investigate this issue error on web console is POST [https://10.10.20.66/graph/login](https://10.10.20.66/graph/login) 401 (Unauthorized) Thanks ---
**Author:** ![ademidoff](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ademidoff/32/14234_2.png) [@ademidoff](https://forums.percona.com/u/ademidoff)\ **Post date:** [October 30, 2025, 11:13am UTC](https://forums.percona.com/t/invalid-username-or-password/39656/2 "2025-10-30T11:13:34Z")
Hi @khaled1 If you have access to the host, could you share the output of the following commands: ```bash docker logs pmm-server docker exec -t pmm-server supervisorctl status ``` Cheers ---
**Author:** ![khaled1](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@khaled1](https://forums.percona.com/u/khaled1)\ **Post date:** [October 30, 2025, 11:19am UTC](https://forums.percona.com/t/invalid-username-or-password/39656/3 "2025-10-30T11:19:00Z")
Below is the logs you asked, by the way I used admin@localhost and it worked, also I created new username and I logged in without @localhost root@rms-pmm:~# docker logs pmm-server Running as UID 1000 Checking /usr/share/pmm-server directory structure… Creating nginx temp directories… Generating self-signed certificates for nginx… Checking nginx configuration… nginx: [alert] could not open error log file: open() “/var/log/nginx/error.log” failed (2: No such file or directory) 2025/10/30 09:27:06 [warn] 15#15: “ssl\_stapling” ignored, issuer certificate not found for certificate “/srv/nginx/certificate.crt” nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful 2025-10-30 09:27:06,706 INFO Included extra file “/etc/supervisord.d/grafana.ini” during parsing 2025-10-30 09:27:06,706 INFO Included extra file “/etc/supervisord.d/nomad-server.ini” during parsing 2025-10-30 09:27:06,706 INFO Included extra file “/etc/supervisord.d/pmm.ini” during parsing 2025-10-30 09:27:06,706 INFO Included extra file “/etc/supervisord.d/qan-api2.ini” during parsing 2025-10-30 09:27:06,706 INFO Included extra file “/etc/supervisord.d/supervisord.ini” during parsing 2025-10-30 09:27:06,706 INFO Included extra file “/etc/supervisord.d/victoriametrics.ini” during parsing 2025-10-30 09:27:06,706 INFO Included extra file “/etc/supervisord.d/vmalert.ini” during parsing 2025-10-30 09:27:06,706 INFO Included extra file “/etc/supervisord.d/vmproxy.ini” during parsing 2025-10-30 09:27:06,708 INFO RPC interface ‘supervisor’ initialized 2025-10-30 09:27:06,709 INFO supervisord started with pid 1 2025-10-30 09:27:07,711 INFO spawned: ‘pmm-init’ with pid 20 2025-10-30 09:27:07,714 INFO spawned: ‘postgresql’ with pid 21 2025-10-30 09:27:07,716 INFO spawned: ‘clickhouse’ with pid 22 2025-10-30 09:27:07,718 INFO spawned: ‘grafana’ with pid 23 2025-10-30 09:27:07,720 INFO spawned: ‘nginx’ with pid 24 2025-10-30 09:27:07,722 INFO spawned: ‘victoriametrics’ with pid 25 2025-10-30 09:27:07,724 INFO spawned: ‘vmalert’ with pid 26 2025-10-30 09:27:07,734 INFO spawned: ‘vmproxy’ with pid 27 2025-10-30 09:27:07,743 INFO spawned: ‘qan-api2’ with pid 31 2025-10-30 09:27:07,751 INFO spawned: ‘pmm-managed’ with pid 35 2025-10-30 09:27:07,811 INFO exited: qan-api2 (exit status 1; not expected) 2025-10-30 09:27:08,710 INFO success: pmm-init entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 09:27:08,722 INFO success: postgresql entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 09:27:08,722 INFO success: clickhouse entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 09:27:08,722 INFO success: grafana entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 09:27:08,722 INFO success: nginx entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 09:27:08,722 INFO success: victoriametrics entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 09:27:08,834 INFO success: vmalert entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 09:27:08,834 INFO success: vmproxy entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 09:27:08,835 INFO spawned: ‘qan-api2’ with pid 371 2025-10-30 09:27:08,836 INFO success: pmm-managed entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 09:27:09,875 INFO success: qan-api2 entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 09:27:10,162 INFO spawned: ‘pmm-agent’ with pid 450 2025-10-30 09:27:11,162 INFO success: pmm-agent entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 09:27:12,228 INFO exited: pmm-init (exit status 0; expected) 2025-10-30 10:18:19,860 WARN received SIGTERM indicating exit request 2025-10-30 10:18:19,860 INFO waiting for postgresql, clickhouse, grafana, nginx, victoriametrics, vmalert, vmproxy, qan-api2, pmm-managed, pmm-agent to die 2025-10-30 10:18:19,867 INFO stopped: pmm-agent (exit status 0) 2025-10-30 10:18:20,068 INFO stopped: pmm-managed (exit status 0) 2025-10-30 10:18:20,070 INFO stopped: qan-api2 (exit status 0) 2025-10-30 10:18:20,071 INFO stopped: vmproxy (terminated by SIGINT) 2025-10-30 10:18:20,072 INFO stopped: vmalert (exit status 0) 2025-10-30 10:18:21,106 INFO stopped: victoriametrics (exit status 0) 2025-10-30 10:18:21,672 INFO stopped: nginx (exit status 0) 2025-10-30 10:18:21,690 INFO stopped: grafana (exit status 0) 2025-10-30 10:18:23,812 INFO waiting for postgresql, clickhouse to die 2025-10-30 10:18:23,870 INFO stopped: clickhouse (exit status 0) 2025-10-30 10:18:23,884 INFO stopped: postgresql (exit status 0) Running as UID 1000 Checking /usr/share/pmm-server directory structure… Generating self-signed certificates for nginx… Checking nginx configuration… nginx: [alert] could not open error log file: open() “/var/log/nginx/error.log” failed (2: No such file or directory) 2025/10/30 10:18:29 [warn] 14#14: “ssl\_stapling” ignored, issuer certificate not found for certificate “/srv/nginx/certificate.crt” nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful 2025-10-30 10:18:29,832 INFO Included extra file “/etc/supervisord.d/grafana.ini” during parsing 2025-10-30 10:18:29,832 INFO Included extra file “/etc/supervisord.d/nomad-server.ini” during parsing 2025-10-30 10:18:29,833 INFO Included extra file “/etc/supervisord.d/pmm.ini” during parsing 2025-10-30 10:18:29,833 INFO Included extra file “/etc/supervisord.d/qan-api2.ini” during parsing 2025-10-30 10:18:29,833 INFO Included extra file “/etc/supervisord.d/supervisord.ini” during parsing 2025-10-30 10:18:29,833 INFO Included extra file “/etc/supervisord.d/victoriametrics.ini” during parsing 2025-10-30 10:18:29,833 INFO Included extra file “/etc/supervisord.d/vmalert.ini” during parsing 2025-10-30 10:18:29,833 INFO Included extra file “/etc/supervisord.d/vmproxy.ini” during parsing 2025-10-30 10:18:29,836 INFO RPC interface ‘supervisor’ initialized 2025-10-30 10:18:29,836 INFO supervisord started with pid 1 2025-10-30 10:18:30,840 INFO spawned: ‘pmm-init’ with pid 19 2025-10-30 10:18:30,844 INFO spawned: ‘postgresql’ with pid 20 2025-10-30 10:18:30,846 INFO spawned: ‘clickhouse’ with pid 21 2025-10-30 10:18:30,847 INFO spawned: ‘grafana’ with pid 22 2025-10-30 10:18:30,849 INFO spawned: ‘nginx’ with pid 23 2025-10-30 10:18:30,851 INFO spawned: ‘victoriametrics’ with pid 24 2025-10-30 10:18:30,853 INFO spawned: ‘vmalert’ with pid 25 2025-10-30 10:18:30,859 INFO spawned: ‘vmproxy’ with pid 26 2025-10-30 10:18:30,870 INFO spawned: ‘qan-api2’ with pid 30 2025-10-30 10:18:30,875 INFO spawned: ‘pmm-managed’ with pid 34 2025-10-30 10:18:30,922 INFO exited: qan-api2 (exit status 1; not expected) 2025-10-30 10:18:31,868 INFO success: pmm-init entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 10:18:31,868 INFO success: postgresql entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 10:18:31,869 INFO success: clickhouse entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 10:18:31,869 INFO success: grafana entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 10:18:31,869 INFO success: nginx entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 10:18:31,869 INFO success: victoriametrics entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 10:18:31,869 INFO success: vmalert entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 10:18:31,869 INFO success: vmproxy entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 10:18:31,925 INFO spawned: ‘qan-api2’ with pid 373 2025-10-30 10:18:31,925 INFO success: pmm-managed entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 10:18:32,126 INFO exited: qan-api2 (exit status 1; not expected) 2025-10-30 10:18:33,350 INFO spawned: ‘pmm-agent’ with pid 453 2025-10-30 10:18:34,132 INFO spawned: ‘qan-api2’ with pid 513 2025-10-30 10:18:34,516 INFO success: pmm-agent entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 10:18:35,166 INFO success: qan-api2 entered RUNNING state, process has stayed up for \> than 1 seconds (startsecs) 2025-10-30 10:18:35,310 INFO exited: pmm-init (exit status 0; expected) root@rms-pmm:~# root@rms-pmm:~# root@rms-pmm:~# docker exec -t pmm-server supervisorctl status clickhouse RUNNING pid 21, uptime 0:58:43 grafana RUNNING pid 22, uptime 0:58:43 nginx RUNNING pid 23, uptime 0:58:43 nomad-server STOPPED Not started pmm-agent RUNNING pid 453, uptime 0:58:40 pmm-init EXITED Oct 30 10:18 AM pmm-managed RUNNING pid 34, uptime 0:58:43 postgresql RUNNING pid 20, uptime 0:58:43 qan-api2 RUNNING pid 513, uptime 0:58:39 victoriametrics RUNNING pid 24, uptime 0:58:43 vmalert RUNNING pid 25, uptime 0:58:43 vmproxy RUNNING pid 26, uptime 0:58:43 ---
**Author:** ![ademidoff](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ademidoff/32/14234_2.png) [@ademidoff](https://forums.percona.com/u/ademidoff)\ **Post date:** [October 30, 2025, 11:47am UTC](https://forums.percona.com/t/invalid-username-or-password/39656/4 "2025-10-30T11:47:35Z")
Thanks. From the logs everything looks good as I can see. Indeed, to log in to PMM the username without the “@localhost” must be used.