root@pam

  1. S

    I can't login w/ root account via SSH/Shell after ingress PVE on AD domain

    Hi. I instaled a PVE7.4 on Dell R710. Setup a VM Win2019 server w/ AD. Setup others VMs, Windows and Linux. I can login in any VM normally with my AD user. On web interface of PVE, i setup de AD and be able to login in. All rigth. But, now, i can't login via ssh or shell w/ root user or my...
  2. A

    [SOLVED] Disabled root@pam. No more webUI access

    I disabled the root@pam unintentionally. Now I really cannot figure out how to re-enable it through the cli of my node. Now, I have no access to the Web UI. I thought about changing the line in etc/pve/user.cfg. However, I have no clue how to change it and if that is the correct way. Anyone has...
  3. F

    Root problems

    Months back I disabled the root account on my cluster. Now I'd like to add another node to my cluster, but it requires root's password. After enabling root again, I am unable to log in via the web GUI with root@pam. All other logins work fine. I can SSH just fine with root@pam as well...
  4. S

    [SOLVED] Disabling root user...

    Greetings, I was trying to secure my new Proxmox install and I disabled root user. I have another user with admin role... It was a big mistake, and now I can't access to Proxmox web interface. I searched on logs but see nothing. I reactivated root user without effect. (pveum usermod root@pam...
  5. T

    deactivated root@PAM - how to reactivate [SOLVED]

    Hi guys I was fondeling around the the GUI. And I deactivated the PAM login and now I can't loginto the WEB-GUI. I know stupid me... but am learning by doing ... xD Could someone post me the path to reactivate it via CLI thaaaanks !!
  6. A

    "Create Cluster" action is not allow for an administrator

    Hi, I would try the new Proxmox 5.2 and I want use "Create Cluster" feature. But, I use proxmox authentication and I have disabled the root linux account. When I use this feature with my administrator account, I have this error : Permission check failed (user != root@pam) (403) Why only linux...