Search results for query: "cipher"

Hello, I'm starting to set up a new Debain 12 server with Plesk, both brand-new installations: Product version: Plesk Obsidian 18.0.59.1 OS version: Debian 12.5 x86_64 When installing DrWeb the following error shows: Copyright (c) Igor Daniloff, 1992-2024 Doctor Web, Moscow, Russia...

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

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

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

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

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

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

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

I just found your question. If it is still open then it could help to look in Plesk-UI for websites/domains/your domain/ssl-certificates/serverconfiguration. Here you can choose an appropriate variant for TLS/ciphers provided by mozilla which comes together with relevant ciphers. If you do this...

Hi, I have enabled the mysql configuration on localhost (127.0.0.1) to require secure connections and verified within mysql /s but still get the fatal error from Plesk when tls.enable =true. : [mysqld] ssl-ca=/etc/mysql/certs/ca-cert.pem ssl-cert=/etc/mysql/certs/server-cert.pem...

@Peter Debik I understand that the issue only occurs when emails arrive from one specific sender, but not from other senders. And only if these emails from that one sender are forwarded, the header character encoding is changed. // yes The problem starts when the content of the mail sent to...

@DragonMaster Please feel free to open a new thread for a new problem to discuss. The cipher issue is not linked with the question about an update.

If you arent looking for a specific kind of setup. But just want to be compliant with the current best practices for SSL configuration, following one of the 3 levels of configuration current defined in: Mozilla SSL Configuration Generator Modern: Services with clients that support TLS 1.3...

root@cloud:~# plesk installer stop Plesk Installer is not running. root@cloud:~# 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...

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