Search results

If none of your outgoing mail is wrongfully classified as spam, you don't need to enable this option. What this option does is relatively fully explained in the hint text: The problem: some software (specifically, web applications, such as CMS'es) may send mail with incorrect settings (wrong...

@Wiz , glad to hear your original problem is resolved. As for check-quota failures, you may try setting null_sender attribute to a full mail address.

@Ian Collier , you have outdated package installed. Please update to the latest version. You may use the following command: plesk installer update

To those affected: please also check your package versions. Run either of the following commands and post the output here. dpkg -l 'plesk-mail-*-driver' | cat # if you have Debian or Ubuntu rpm -qa | grep 'plesk-mail-.*-driver' # if you have RedHat, CentOS, or CloudLinux Thank you.

SSH public keys (deployment keys) are used for client identification. Host public keys (which are stored in .ssh/git_known_keys file in this case) are used for server identification. These are two different entities. I suggest trying option (1) that was outlined in the previous post -- just...

This means that ssh-keyscan -H bitbucket.org has failed to retrieve any keys. This may happen due to a number of reasons, including networking issues between your box and BitBucket. As a workaround you may try either of the following: Use SSH on port 443 as suggested at the bottom of...

@x86, are you sure you're having the same error. I don't see the error message from Apache itself in your post. Please check Apache error logs for details - why it could not be restarted. If you haven't done a dist-upgrade from Debian 7 lately it's seems unlikely that you've got the same...

Most likely autoinstall.plesk.com on your server points to a partial mirror instead of the official download site. To use the official download site make sure /etc/hosts doesn't have autoinstall.plesk.com entry and /etc/resolv.conf uses public DNS servers (e.g. 8.8.8.8 and 8.8.4.4 to use Google...

Docker itself has a number of serious issues (including security ones) that prevent safe usage in a shared hosting environment. That's why Plesk doesn't support Docker usage in shared hosting scenarios.

@solucionesuno, root has the same uid 0 on all systems, therefore you won't have problems with DB restore on another server (as long as you have root access on it). However, please note that MySQL DB is not the only thing that would need to be "restored" if you're doing it on another server...

Please check https://talk.plesk.com/threads/pi-331-plesk-installer-error-with-de-de-locale.339620/#post-811596 Most likely you just need to properly set up locales on your Ubuntu box.

@BobClaas, please either use command line as suggested above (just run plesk installer in shell as root) or launch Plesk Installer web interface from Tools & Settings > Updates & Upgrades.

https://kb.plesk.com/en/130419

It depends on the license type. Plesk Installer will warn you if your license would not work after upgrade to Plesk Onyx.

You can install Courier-IMAP instead (available as Plesk component), and then after migration is finished you may switch it to Dovecot. This way UIDLs should be preserved.

Please make sure you have access to both ext.plesk.com and autoinstall.plesk.com from the servers.

Looks OK to me. Please check if DB is accessible locally by running the plesk db command. It should open MySQL prompt. Please also check that MariaDB daemon service is running. Which device is mounted to /var/lib and /var/run in your case? Is there anything unusual there?

Those are two separate events. There was an issue with update 8 that caused problems with Dovecot under certain update settings. It is already fixed (manual fix is to install the latest version of the 'plesk-dovecot-imap-driver' package, which should now happen automatically for all applicable...

This is not a bug. This just means that another application is using the system package manager. To prevent issues with concurrent usage of package manager Plesk Software Update checks whether another Plesk Installer or Software Update instance is already running.

Placing a mail handler in a given queue should be guided by the use case. Maybe you need before-local queue instead. Unfortunately, I am not aware of yours. As long as handler type is global for before-remote, it will indeed fire for any mail that goes through Postfix smtpd milters subsystem...