Search results for query: "cipher"

# cat /etc/proftpd.conf ... <IfModule mod_tls.c> # common settings for all virtual hosts TLSEngine on TLSRequired on TLSLog /var/log/plesk/ftp_tls.log TLSRSACertificateFile /opt/psa/admin/conf/httpsd.pem TLSRSACertificateKeyFile...

Oh, I see. For me this was not clear that it's an issue with the software that won't start at all. I thought you focussed on the license message. Have you already seen this article...

The support team solved my problem, the issue was: Missing TLSv1.3 ; I installed it and the command works! Thanks for your help!!

@Leonardo N , could you please post the output of the `plesk version` command and check the output of the command `plesk sbin sslmng --show-config` (c)...

I added a new domain and checked the conf files. They all show the certificate of the VPS host. I then performed the SSL configuration and checked the configuration files and none were updated. I next performed a restart of apache and nginx from the services console. Still no configuration files...

You can try this: 1. Log in the server via GUI. 2. Navigate to Tools&Settings > TLS versions and ciphers management > Settings 3. Update cipher by clicking on sync now 4. Re-try to configure outlook or mobile client. or this: 1. Access the server over SSH. 2. Open the following file in text...

also: root@hostname:/var/log/plesk-roundcube# openssl s_client -connect localhost:993 -starttls imap CONNECTED(00000003) Didn't find STARTTLS in server response, trying anyway... write:errno=32 --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 0...

Hey! When trying to connect FTP over TLS via FileZilla, I got this output: 02:51:25 Status: Disconnected from server 02:51:25 Status: Connecting to 1.2.3.4:21... 02:51:25 Status: Connection established, waiting for welcome message... 02:51:26 Response: 220 ProFTPD...

We have made several tests with Curl and several Curl versions however, we are still getting the previous errors. Also, we have tested the following command openssl s_client -connect yourserver.com:443 -alpn h3 CONNECTED(00000003) 140579260147008:error:14094460:SSL...

Hello everyone, i think hackers are abusing phpmailer script on my webpage. I received over 5000 mails in couple of minutes like this: In the not delivered mails i see this log: And in plesk i see there are 35k mails delayed but if i click it i don't see anything Under Action Logs i...

this may be related to the openssl version in use, resp. the ciphers accepted. on newer os (like almalinux 9 resp. centos) this error is caused by the default crypto policies applied. in this case openssl does neither create nor verify sha1 signatures. a quick workaround is to switch to weak...

Ok. The output of your command shows: mail:~# openssl s_client -starttls smtp -showcerts -connect mail.leagues-united.de:587 CONNECTED(00000003) depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1 verify return:1 depth=1 C = US, O = Let's Encrypt, CN = R11 verify return:1...

Hello, i'm trying to update from debian 11 to debian 12 with this tutorial: https://support.plesk.com/hc/en-us/articles/12377714344983-How-to-perform-dist-upgrade-procedure-on-Linux-server-with-Plesk On last step 23, after executing "plesk repair installation", i get an error: Trying to...

It depends on the Outlook version. Did you activate the "Modern ciphers" in Plesk? That will only allow clients that support TLS 1.3. The Intermediate ciphers have a fallback to TLS1.2. That's the recommended setting.

"lowering" the TLS level helps circumvent the problem, because it allows the client to fall back to a different (normally "less" secure) cipher. Microsoft seems to have broken something with cipher suites on this update and TLS connections using these ciphers will fail. If the server does not...

"plesk repair installation" - after a while following comes endlessly: Dou you have an idea how I can fix this, that for plesk repair can finish? P.S.: The output before the endlessly is: Thank you again! :D

The alternate.ka.plesk.com URL is correct. All Plesk versions 12.x and older are managed by it. On that infrastructure Plesk provides legacy SSL/TLS versions and ciphers for similar cases like the one that you experience. For the case that you describe above the recommendation is to obtain the...

I think it is much better to discuss the topic with some real data to show details. If you do not want to use details about your servers, let's use my :) Why do you not use the "-servername" option when checking SNI? In the example below, plesk.domain and mail.domain are different, but with...

Use sslscan to check your SMTP server and the senders SMTP which protocol and ciphers are supported.

Admin user, from the overview page. I just realized that I see the scheduled tasks from the Tools&Settings page.. I tried running the plesk repair installation command before that, which resulted in an error and now mails are not relayed anymore: Executing: /lib/systemd/systemd-sysv-install...