Search results for query: "cipher"

Hi, We have just upgraded our Plesk installation to the latest version available (18.0.53 -> 18.0.54). Then after the successful installation we switched from Postfix to MSMTP according to your installation instructions on...

strange thing is that I get it also on the native mail now when I add a new account on it. It does show the e-mail, bit get an error about the SSL not trusted. SSL I renewed just in case, as when I show the details it shows valid until Feb/2023. On iPhone I don't get the errors, but the...

Another reason for Outlook to refuse the connection: if in the SSL/TLS settings the Plesk admin forces "Recommended by Mozilla standards". It enables too new cipher modes that MS Outlook just doesn't support yet (while all the modern browsers do).

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...

Hello, I'm currently trying to enable TLS1.0 and TLS1.1 on my linux server. By default TLS1.2 and TLS1.3 are enabled and various online tools show that only those two are enabled. I have tried to enable 1.0 and 1.1 via the Plesk overlays option "TLS versions and ciphers by Mozilla", setting...

Yes, I know, but I'm not concerned about that point. Anyway, thanks for letting me know The most consistent option that I can think of (and my hope, because I would like to say that the problem has been solved) is that this process of this one that was "zombie" had an erroneous certificate in...

Hello,thank you! I checked the headers,thats what i get: Delivered-To: [email protected] Received: by 2002:a05:7508:290b:b0:7e:968b:4c7 with SMTP id ev11csp51441gbb; Sat, 5 Oct 2024 15:55:12 -0700 (PDT) X-Google-Smtp-Source...

In the past I have choosen for TLS-versions and cyphers the mozilla "modern" variant. The last days I got calls from users that E-Mail send/receive via my server didn't work any longer. So I found out, that the variant modern of Mozilla has changed and does now only use TLSv1.3 what does not...

For TLSv1.2 and TLSv1.3, We are using this configuration in Nginx. This works fine for majorly all browsers. ssl_protocols TLSv1.2 TLSv1.3; ssl_prefer_server_ciphers on; ssl_ciphers...

Repairing PLESK gives the error below with FAILED Reconfiguring the Plesk installation Started bootstrapper repair procedure. This may take a while. Certain actions may be skipped if not applicable. Finishing up upgrade procedures and rerunning previously failed upgrade actions... ===>...

1. TLS I have tried all of them, not one of them works. 2. No difference. 3. This is correct, the correct config is applied, it is a default Plesk installation (a new one) I have checked against other servers that I have, I can not see any differences, that is the puzzling part.

Understood. From the original post, thought it was somebody else, that had included some details of their Plesk Support Team findings, within another thread. That will be just as the Plesk Support Team and yourself expected. That's good. However, unless you've made some pretty significant...

@Kaspar Steps: Following these Securing Connections to a Remote MySQL Database Server : Environment (Both machines same VNET): VM 1 - Ubuntu 18.04.6 LTS - VM 1 Plesk/MySQL 5.7.* (mysql added on localhost to Plesk) VM 2 - Ubuntu 18.04.6 LTS - VM 2 MySQL 5.7.* (this remote mysql instance also...

Hi, I think that the problem is somewhere over php.it (panel.ini) of plesk, because if I try to make this test I have no error curl -v https://google.com * Trying 142.250.184.110:443... * Connected to google.com (142.250.184.110) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 *...

plesk repair installation: Reconfiguring the Plesk installation Started bootstrapper repair procedure. This may take a while. Certain actions may be skipped if not applicable. Finishing up upgrade procedures and rerunning previously failed upgrade actions... ===> Cumulative Plesk database...

I've changed the following three params in /etc/postfix/main.cf The first two allow all TLS version supported by your postfix/openssl (except SSLv2 and SSLv3) and the third adjusts the available cipher suites. (without them, TLS 1.0 and TLS 1.1 do not work properly)...

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...

I suffered for hours on this problem so I decided to post it here for future searchers. Basically I moved my website to my new server hosted by Ionos. We run Woocommerce on Wordpress and use a Shipstation plugin to update orders. We I transferred over the website to the new server, the...

As stated in https://support.plesk.com/hc/en-us/articles/115000422229-How-to-enable-disable-TLS-protocol-versions-in-Plesk-for-Linux, TLS 1.3 isn't available in Apache on CentOS 7. The "plesk bin server_pref -u -ssl-ciphers" command changes settings for both Apache and nginx and therefore can't...

Most likely the problem is that your Plesk/Postfix server is configured to run with TLS 1.2 (and newer), but your Windows/Apache/PHP server does support TLS 1.0/1.1 only So you will either need to change your Plesk/Postfix server to support these older TLS versions as well, or you need up...