Recent content by KirkM

But it appears it is needed for full functionality as the disk data can't be fetched without it and it literally throws an error message in Plesk if you use the extension and go to the panel page to review the data. That really doesn't sound "optional" to me.

Thank you, that was the issue. So it is a faulty installation of the Process List extension? Wouldn't the extension install all dependencies to properly function? Although this fixes the issue, I am concerned about the root cause of the problem and making sure if there is a flaw in the...

Going to the Process List in the Plesk Panel shows this error. Notice the extra forward slash in the script path (modules//repair) where either it is a typo or a directory is missing in-between. I assume this is somewhere in the Process List extension code. Bug? Faulty installation? Thanks...

I used the Plesk migrator to migrate one of a few Sitejet sites to a new server. The first one was a simple site and all went smoothly. It works on the new server and I can edit in Sitejet the same as when it was on the old server. The second Sitejet website that was migrated seemed to be...

They have disabled the ability to mark as resolved, but it is resolved!

It was set to hashing. Changing it to Symmetric encryption did the trick. Thank you so much!

Full error: And yes, the username and passwords are correct.

A bit more detail - Both the successful tests with the old domains and the failures with the new domains settings are: Username: [email protected] Password: {password} TLS, Port 587 Postfix / Dovecot I have tried: opening all ports on the firewall Disabling the firewall uninstalling the...

When I test smtp on new email addresses on any domain on my server with PHPMailer smtp test script and v7.0.1, I get Existing domains before the update are fine when do the exact same test but any new ones always fail with the identical setups on the same server and even the same domain.

Read the second paragraph in this section from the 2026 document you listed as Source 2: https://cdn1.plesk.com/wp-content/uploads/pdf/b2a5u/Plesk_Customer_Licensing_Guide_2026.pdf: If nothing else, they got balls to gaslight like that right to our faces. Either balls or raging contempt for...

Great! ssl=yes works but it looks like you have configured your system to force ssl. Glad you got it sorted out.

I noticed you don't have a reference to the dh pem file at the top. This is getting a bit over my head, but I see that as a difference between our config files. ssl_server_dh_file=/usr/local/psa/etc/dhparams2048.pem Not sure if that would be the cause or not.

So is encryption working now? My accounts are all working with encryption on all devices.

Looks like Plesk has released the mu patch.

My mail connections still appear to be encrypted. Are you missing any lines like this: ssl_min_protocol=TLSv1.2