Search results

Thanks for the solution, which I used earlier today. However, it is "all just a little bit ****" that there is no way to do this through the Plesk Panel.

I'm about to migrate a whole load of Plesk users from one server to another, so I want to put an announcement notice & link up on the login page, which will help users it they try to log in via the old server's login page.

That doesn't work. I get the following error:

Not doing well today. I also found that the last option should be -srv-weight instead of --srv-weight. :rolleyes:

Just after posting, I looked back at the documentation and found that I had missed the '' parameter after the -srv parameter.

I'm using the Plesk CLI to script the changing of some SRV DNS records. I'm following the documentation at dns: DNS Zones on Domains I'm sending in a command (domain changed): plesk bin dns --add example.com -srv -srv-service imaps -srv-target-host mail.other.com. -srv-protocol TCP -srv-port...

There is an existing feature request in for this... I suggest that you up-vote this: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/34108849-add-mailman-support-to-let-s-encrypt There's an existing user solution, but I'd much rather that Plesk implement something that...

I agree completely. It is more than a little silly to require a password for a forwarding alias. Users find it confusing too, which leads to higher workload on support teams.

I've got exactly the same issue as this. Email subject: Plesk key update deferral notification Email content: Unable to update EXT.05294193.0020: an error occurred while processing your key. You can try to retrieve the key manually in Plesk (Tools & Settings > License Management) or let Plesk...

Could you possibly give a non-binding indication of when the next release is likely be please? Are we talking approximately 1 week, 3 weeks, 6 weeks, etc.?

I'm still having his issue with Roundcube 1.4.1 and Plesk 17.8.11 Update #74. Although there is a workaround, it isn't great that the API calls are failing because non-technical users have chosen to configure captial letters in their email addresses. Can the plesk API code or user interface be...

Currently running Roundcube 1.3.10 and Plesk 17.8.11 Update #67. We've just had another user fall fowl of this bug. Any news on possibly reproducing and fixing this issue?

Indeed. Disappointing that the "guru" users were so dismissive of your valid report.

Thanks noisycity! I've uninstalled the SEO Toolkit. The 7.5GB file at /usr/local/psa/var/modules/xovi/xovi.sqlite3 disappeared and my server is no longer in danger of running out of space in this partition. You're not alone in suffering from this. IMO it is definitely a Plesk failure to have...

Hi Mark, Thanks for your message. I've checked and this is already using the default of 2. The request sent in the Plesk XML API is lowercase in both examples (excerpt from above logs): <packet...

I've upgraded Roundcube to 1.3.5 (server still running Plesk Onyx Version 17.5.3 Update #43) and get the same behaviour as before (failing when the email alias has an uppercase character in it). Are there any differences between the Roundcube package bundled with Plesk and the package that is...

Thanks @IgorG. I'll upgrade Roundcube and test again.

We've now done more work and added logging around the line of plugins/password/driver/plesk.php which calls the "curl_exec". This has successfully captured the XML Request and XML Response from each CURL execution. We've also changed plugins/password/password.php so that it logs to...

TITLE: Roundcube Password add-in fails due to case sensitive email address PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: Plesk Onyx Version 17.5.3 Update #43 CentOS release 6.9 (Final) Roundcube v1.2.3 (non-Plesk version) [oops - needs updating!] PROBLEM DESCRIPTION: An email mailbox is...