[SOLVED] Cannot login to web UI (root)

[wav3front]

Hi,

All of sudden I cannot login to my web GUI. I get the message:

"Login failed. Please try again"

I can login to ssh normally.

The last time I logged in was about 3 weeks ago and it was working.
The server is not a part of a cluster, just stand-alone Proxmox VE.

Any ideas?

Thanks
Alex

 

[wav3front]

journal log contains:

Oct 18 21:34:25 ns31568010 IPCC.xs[2103835]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:79.**.***.*** user=root

 

[bbgeek17]

Hi @wav3front ,

Are you sure you are using the correct authentication method, i.e. PAM vs PVE?
Do you have space on the root disk?
Are all the services running? (systemctl status|grep pve)
Have you tried different browser or incognito mode?
Are you sure that you don't have any browser extensions that are interfering and swapping the password?

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[wav3front]

Hi, thank for your message.

I've tried 4 different browsers.

-Do you have space on the root disk?
not sure. how do I check that?

systemctl status|grep pve output, apart from the VM info:

│ ├─pve-cluster.service
│ ├─pve-firewall.service
│ │ └─1739 pve-firewall
│ ├─pve-ha-crm.service
│ │ └─1777 pve-ha-crm
│ ├─pve-ha-lrm.service
│ │ └─1801 pve-ha-lrm
│ ├─pve-lxc-syscalld.service
│ │ └─1333 /usr/lib/x86_64-linux-gnu/pve-lxc-syscalld/pve-lxc-syscalld --system /run/pve/lxc-syscalld.sock
│ ├─pvedaemon.service
│ │ ├─ 1767 pvedaemon
│ │ ├─2094131 "pvedaemon worker"
│ │ ├─2103835 "pvedaemon worker"
│ │ └─2109582 "pvedaemon worker"
│ ├─pvefw-logger.service
│ │ └─27457 /usr/sbin/pvefw-logger
│ ├─pveproxy.service
│ │ ├─ 1792 pveproxy
│ │ ├─27462 "pveproxy worker"
│ │ ├─27463 "pveproxy worker"
│ │ └─27464 "pveproxy worker"
│ ├─pvescheduler.service
│ │ └─1806 pvescheduler
│ ├─pvestatd.service
│ │ └─1741 pvestatd
│ └─519919 grep pve

 

[wav3front]

Here's some disk info:

root@*****:~# df -h | grep -v Used | awk '{ print $1" " $5 "\t" }'
udev 0%
tmpfs 1%
/dev/md3 21%
tmpfs 1%
tmpfs 0%
efivarfs 12%
/dev/md2 11%
/dev/mapper/vg-data 35%
/dev/nvme1n1p1 2%
/dev/fuse 1%
//**********.your-storagebox.de/backup 15%
tmpfs 0%

 

[wav3front]

Are you sure you are using the correct authentication method, i.e. PAM vs PVE?

yes. pam

 

[bbgeek17]

Please surround your output with CODE (</>) tags, from the edit box menu at the top.

Since you are able to run CLI commands, that implies you can access the console directly. Are you using physical console or SSH?

What happens when you run the following from the console:
curl -k -d 'username=root@pam' --data-urlencode 'password=[PASSWORD]' https://localhost:8006/api2/json/access/ticket

Have you implemented, and forgot, about fail2ban or equivalent? Is the root user, perhaps, restricted due to a number of failed login attempts?

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[wav3front]

Have you implemented, and forgot, about fail2ban or equivalent? Is the root user, perhaps, restricted due to a number of failed login attempts?

Yes. I'm pretty sure that's the case.

This is what happens when I run that command:

root@ns*****:~# curl -k -d 'username=root@pam' --data-urlencode 'password=************' https://localhost:8006/api2/json/access/ticket
{"data":null}root@*****:~#

 

[wav3front]

I changed password for root user via cli and now it works.

 

[bbgeek17]

Good to hear.
You can mark the thread as "solved" by editing original post and changing the subject prefix

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox