• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue cURL error 35: OpenSSL SSL_connect: Connection reset by peer in connection to

boutiquepcland

New Pleskian
Server operating system version
OS: Ubuntu 22.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.67 Mise à jour 3
Hello everyone, for about 6/8 months, I regularly have messages in the wordpress backoffices like cURL error 35: OpenSSL SSL_connect: Connection reset by peer in connection to nomdedomain.com:443 I asked Plesk support but without success! sometimes I take the time to make a command line for example dig +short gravityapi.com A then I take the IPs then I put it in the host file to bypass the error message!

The idea is to do this manipulation! does anyone have an idea of what it blocks? How to solve the problem?

Thanks in advance.
 
Hi!

To be honest, I have not clearly understood how the components in your environment are connected to each other and what components are under your control. It seems the issue is somewhere in connections, firewalls, etc.

To exclude additional software from the investigating, have you tried to execute the same commands from the same server but right in CLI/SSH (without WordPress and Plesk)? E.g., when the issue happens, run the `curl` command from the same IP address to the same host. If the issue is reproducible, it makes sense to try the same without a firewall, etc.
 
When I do the curl command with the domain or the IP nothing blocks, but with the server IP, but for me the sites have a failover IP! no firewall nothing!
 
Back
Top