Gunicorn requiring password for service user on new system?

[tromlet]

Describe the bug
The service cannot start due to some kind of a user login issue - the system appears to be trying to do a password login on a local user, and I don't think it needs to do that.

To Reproduce
Steps to reproduce the behavior:

1. SCP your wg-manager directory from a working CentOS 7 server to a new, Alma Linx 8.10 server
2. Create a new service file /etc/systemd/system/wg-manager.service on your new server, copy the contents of the old one to this new one
3. Create requisite service user, vpn
4. chown -R vpn:vpn /opt/wg-manager
5. Try starting the service. You'll get this error with journalctl -u wg-manager.

Platform:

• OS: Alma Linux 8.10

Stacktrace/error output
This is the error I get when I run journalctl -u wg-manager:

Jan 22 19:23:52 wg.example.com sudo[5535]: pam_unix(sudo:auth): conversation failed
Jan 22 19:23:52 wg.example.com sudo[5535]: pam_unix(sudo:auth): auth could not identify password for [vpn]
Jan 22 19:23:52 wg.example.com gunicorn[5535]: sudo: a password is required
Jan 22 19:23:53 wg.example.com gunicorn[5537]: We trust you have received the usual lecture from the local System
Jan 22 19:23:53 wg.example.com gunicorn[5537]: Administrator. It usually boils down to these three things:
Jan 22 19:23:53 wg.example.com gunicorn[5537]:     #1) Respect the privacy of others.
Jan 22 19:23:53 wg.example.com gunicorn[5537]:     #2) Think before you type.
Jan 22 19:23:53 wg.example.com gunicorn[5537]:     #3) With great power comes great responsibility.
Jan 22 19:23:53 wg.example.com gunicorn[5537]: sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper

Additional context
I copied and pasted my /opt/wg-manager directory from a CentOS 7 server to /opt/wg-manager on a fresh, new, Alma 8.10 server. I'm trying to just migrate this thing to a server that still gets security patches, and then I'll work on getting it onto a different WireGuard manager.

I do not see any fancy differences between the users in the /etc/passwd file, I made sure they're both in wheel, but I DO notice a SLIGHT difference in /etc/pam.d/sudo between each system:

CentOS 7:

#.d/sudo
#%PAM-1.0
auth       include      system-auth
account    include      system-auth
password   include      system-auth
session    optional     pam_keyinit.so revoke
session    include      system-auth

Alma 8.10:

# cat /etc/pam.d/sudo
#%PAM-1.0
auth       include      system-auth
account    include      system-auth
password   include      system-auth
session    include      system-auth

Not sure what I've done here?