• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Polkit error

Giuseppe

Basic Pleskian
Hello al,
i have an issue when launch any Plesk repair command.

Exit the error:
** (pkttyagent:32483): WARNING **: 20:18:22.522: Unable to register authentication agent: GDBus.Error:eek:rg.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject
Error registering authentication agent: GDBus.Error:eek:rg.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject (polkit-error-quark, 0)

I not found any info about solution of this issue :(

I have: CentOS Linux 7.9.2009 with Plesk 18.0.32

Thanks
Giuseppe
 
I think I remember having seen this or a very similar error before. It was not linked to Plesk, but a mismatch between the Linux kernel version and other OS components, because after a "yum upgrade" the machine was no rebooted. A reboot of the machine was necessary to bring it back into sync. Not sure whether it applies to your case though.
 
Back
Top