[GH-ISSUE #970] pam_unix(sudo:auth): authentication failure; logname=root #824

New issue

Closed

opened 2026-02-27 11:13:45 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 11:13:45 +03:00

Owner

Originally created by @uberdave on GitHub (Nov 23, 2016).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/970

My site refuses to connect with a pam error.(nginx won't restart)

pam_unix(sudo:auth): authentication failure; logname=root

from tail -f auth.log, when connecting:: session opened for user vmail by (uid=0); pam_unix(cron:session): session opened for user root by (uid=0); pam_unix(cron:session): session closed for user root; pam_unix(cron:session): session closed for user vmail

journalctl -xn for nginx
pam_unix(sudo:auth): authentication failure; logname=root uid=1000 euid=0 tty=/dev/pts/0

Originally created by @uberdave on GitHub (Nov 23, 2016). Original GitHub issue: https://github.com/modoboa/modoboa/issues/970 My site refuses to connect with a pam error.(nginx won't restart) pam_unix(sudo:auth): authentication failure; logname=root from tail -f auth.log, when connecting: : session opened for user vmail by (uid=0) : pam_unix(cron:session): session opened for user root by (uid=0) : pam_unix(cron:session): session closed for user root : pam_unix(cron:session): session closed for user vmail journalctl -xn for nginx pam_unix(sudo:auth): authentication failure; logname=root uid=1000 euid=0 tty=/dev/pts/0

kerem closed this issue

2026-02-27 11:13:45 +03:00

kerem commented

2026-02-27 11:13:46 +03:00

Author

Owner

@tonioo commented on GitHub (Nov 23, 2016):

Can you give more information about your context? How did you install Modoboa? What is your actual problem?

@tonioo commented on GitHub (Nov 23, 2016): Can you give more information about your context? How did you install Modoboa? What is your actual problem?

kerem commented

2026-02-27 11:13:46 +03:00

Author

Owner

@uberdave commented on GitHub (Nov 23, 2016):

I used the easy install on debian 8. at first the admin panel came up. Then I reinstalled with letsencrypt.
when I revisited the site, I was not able to load anything as, nginx failed to reboot, as I documented earlier. Since then, as I am on a vps, I rebuilt my droplet on Centos 6, and everything seems to be ok now, but I am going to wait a while before I try letsencrypt, again. I want to thank you guys for your hard work and what appears to be great software! I will be following. You can go ahead and close this, and, i'll post again, if the same thing happens again later with letsencrypt.

@uberdave commented on GitHub (Nov 23, 2016): I used the easy install on debian 8. at first the admin panel came up. Then I reinstalled with letsencrypt. when I revisited the site, I was not able to load anything as, nginx failed to reboot, as I documented earlier. Since then, as I am on a vps, I rebuilt my droplet on Centos 6, and everything seems to be ok now, but I am going to wait a while before I try letsencrypt, again. I want to thank you guys for your hard work and what appears to be great software! I will be following. You can go ahead and close this, and, i'll post again, if the same thing happens again later with letsencrypt.

kerem commented

2026-02-27 11:13:46 +03:00

Author

Owner

@tonioo commented on GitHub (Nov 23, 2016):

Ok, thank you for the feedback.

@tonioo commented on GitHub (Nov 23, 2016): Ok, thank you for the feedback.