Search results

You can use the panel.ini Editor to change the mailserver names that Plesk uses for these autodiscover services and info/help pages. Assuming that the DNS record for mail.DOMAIN.TLD points to the server used for email, you would need to add the following lines: [mail]...

We started to use acme.sh for issuing wildcard certificates in such cases If DNS for the domain runs on your Plesk server or any of the ~150 supported DNS servers (see dnsapi · acmesh-official/acme.sh Wiki) the creation and renewal of the certificate will work fully automated and does require...

which directory did you check? I believe that Plesk uses /var/www/vhosts/system/domain.tld/logs/ and not /var/www/vhosts/domain.tld/logs/ for calculating the space usage normally it's the same, as the files in these two directories are hardlinked, but if you for example manually delete stuff in...

This extension does send over all potential malicious files (.php, .js, .css and more) of a website to VirusTotal, so you'll get many requests per site and not just one

So, two years later and still no solution? We see so many customers switching to Wix (and similar) for their website but still want to use our service for email. But good luck with that, as they can no longer use it in a secure way* and it causes so many headaches on our and the customers...

No, it is not possible. Plesk and it's LetsEncrypt support becomes borderline useless, if you don't run the DNS AND WEB service for a domain on the Plesk server. There is also no way to issue a wildcard cert and securing the mail parts of a domain, if the website points to an external server.

For full server backups I'd recommend to not use rsync but a tool/software like the free Veeam Agent for Linux or Acronis Image Backup.

go over to DEB.SURY.ORG and use their repository for PHP 7.4, once Plesk stops providing updates. Sure, there is no guarantee on how long they will support PHP 7.4, but as they still provide security updates for releases back to PHP 5.6 as of today, the chances are high that you'll see a...

I assume that the SSL/TLS configuration of your Postfix service is not working properly in general. Maybe a wrong certificate, missing chain, cipher suite, or one of the many other possible things that can be wrong when it comes to SSL/TLS Maybe a tool/website like Mailserver encryption test...

change/adjust your config.inc.php to: $config['smtp_host'] = 'localhost:25'; $config['smtp_auth_type'] = 'PLAIN'; You most likely have some problem with the SSL certificate/configuration on your SMTP service, thus Roundcube refuses to connect via SSL (port 465) or StartTLS (port 587)

login via SSH, then: rm /etc/nginx/conf.d/cf-stop /root/cf.sh

looks a bit like you forgot the chain/intermediate certificate or added a wrong one? A website like Mailserver encryption test (STARTTLS, TLS and PFS) · SSL-Tools can help identify this.

No, "old" is not recommended to use for anything else than SMTP And as this setting can not be configured per service in the "SSL it" extension, you should use "intermediate" and change the Postfix configuration manually. (the parameters tls_medium_cipherlist, smtpd_tls_protocols and...

We use TLS 1.0/1.1 for Postfix on all our servers and so far it did never got reset (except if we manually click "Sync now" with the Intermediate profile in the SSL it! extension) So it may be quite save, but I can not guarantee that....here we would need a word from the Plesk devs. I would...

old/lost data is lost, no way to get these statistics data back. so you need to wait till next month to see an additional month and so on. Why you see 12 months but only four are populated with data, I don't know. But I only ever work with AWstats, so it's possible that Webalizer does always...

well, with the "old" setting your php script could connect at least, but then failed because either the configured username or password was wrong.

well, for a quick change/check, you can go to "Tools&Settings" --> "TLS versions and ciphers management" and apply the "Old" preset. This will enable TLS 1.0/1.1 (including the required old ciphers) for Postfix - but of course also for nginx, apache, dovecot, proftpd (where you don't wanna...

As far as I know, to change this setting for existing sites, you need to use the CLI (or edit the PSA database directly) This CLI command should be able to do that:

OpenSSL 1.1.1h indicates that your PHP supports TLS 1.2 and even 1.3 (from OpenSSL 1.0.1 on, TLS 1.2 is supported) Most likely something else in your environments is responsible for the "downgrade" to TLS 1.0/1.1 of your SMTP connections. That can either be a firewall or the PHP script itself...

If I am not mistaken, this only depends on the PHP version (i.e. the OpenSSL version PHP was compiled against) and not Windows or Apache2. And for the standard PHP binary releases you can download from the official page (PHP For Windows: Home), everything from PHP 5.6 on should support TLS 1.2