cURL error 56: OpenSSL SSL_read: Connection reset by peer, errno 104 on 3 websit

  • Resolved vshukla

    (@vshukla)


    3 years, 10 months ago

    As advised and in compliance with the forum rules, I am starting a new thread for this issue.

    I have the same problem on all 3 of my websites and have already tried the troubleshooting tips.

    This is a sample from one of them for which I have just emailed the diagnostic report.If required, I can send it for the other 2 websites too.

    1. Unable to do manual update. This error was noticed around 24th January and I chose to wait for the next update which was on 26th January. I am not able to do a manual update.

    The last rules update for the Wordfence Web Application Firewall was unsuccessful. The last successful update check was January 12, 2021 11:25 pm, so this site may be missing new rules added since then. You may wait for the next automatic attempt at February 2, 2021 11:33 pm or try to?Manually Update?by clicking the “Manually Refresh Rules” button below the Rules list.

    2. Scan fail error: I am receiving this message every time I try to do a scan

    Scan terminated with error: There was an error connecting to the Wordfence scanning servers: cURL error 56: OpenSSL SSL_read: Connection reset by peer, errno 104

    I have checked the connectivity and it appears alright. I also am receiving notifications of plugin updates required.

    Please help.

    Thanks in advance

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support WFAdam

    (@wfadam)

    Hello @vshukla and thanks for reaching out to us!

    We are currently seeing this issue from a few of our customers. We are investigating what might be causing it. We have noticed that everyone who is reporting this is using EIG hosting, however. It could be something on how our server communicates with the host.

    Once we have a solution or a path to resolution, we will let you know!

    To help us understand this issue, can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    Thanks!

    Thread Starter vshukla

    (@vshukla)

    Hello @wfadam . I’ve just sent the diagnostic report for karmicallycoaching.com. It’s the same issue as with the other website that I started my ticket with.

    Thread Starter vshukla

    (@vshukla)

    Hello @wfadam. I’ve just sent the diagnostic report for Kusumshukla.com. Same issue as the previous one.

    Please help. Thanks.

    Plugin Support WFAdam

    (@wfadam)

    We might have some good news on this issue!

    Ask your host if they have an outbound proxy or firewall that might limit or close connections because outbound connections from your site to noc1.wordfence.com are intermittently failing. You can also tell the host that these Wordfence servers used to be in the range 69.46.36.0/27 and have recently changed, in case the host had previously whitelisted those and need to whitelist the new IPs 75.2.79.124 and 99.83.193.37.

    Thanks for your help! Please let me know if this helps!

    Thanks!

    Thread Starter vshukla

    (@vshukla)

    Hi @wfadam

    I did as you advised and the host provider white listed the 2 IPs you recommended. I have sent a diagnostic report for vatsalashukla.com.

    Now I’m getting the message

    Scan terminated with error: There was an error connecting to the Wordfence scanning servers: cURL error 35: OpenSSL SSL_connect: Connection reset by peer in connection to noc1.wordfence.com:443

    Thread Starter vshukla

    (@vshukla)

    This is the message I got for Karmicallycoaching.com.

    [FEB 03 21:13:20] Scan terminated with error: There was an error connecting to the Wordfence scanning servers: cURL error 35: OpenSSL SSL_connect: Connection reset by peer in connection to noc1.wordfence.com:443

    I’ve sent the diagnostic report too.

    Plugin Support WFAdam

    (@wfadam)

    Our QA team has suggested there might be an issue with how TLS is being resolved on your host’s end.

    Can you have them, or you can if you’re comfortable doing so, try to run curl -v in the CLI a few times to see if it fails, and what it says.

    Thanks!

    Thread Starter vshukla

    (@vshukla)

    How does one do this on one’s own? My websites are on a shared server.

    Plugin Support WFAdam

    (@wfadam)

    You will want the host to run this command in CLI a few times:

    curl -v https://noc1.wordfence.com/

    It should normally end with a message saying Your site did not send an API key when contacting the Wordfence servers. if it’s successful.

    Let me know the results!

    Thanks!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘cURL error 56: OpenSSL SSL_read: Connection reset by peer, errno 104 on 3 websit’ is closed to new replies.