• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

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