Plesk domains and various actions like updating WordPress plugins do not work under CentOS 7: cURL error 77

Follow

Comments

11 comments

  • Avatar
    Mickael Boud (Edited )

    Thanks a million Alexander-Davydov for having shared this. You helped me fixed major issues blocking payments from our WordPress woocommerce based ecommerce website. The curl requests were triggering this code 77 error.
    And it looks like looots of online merchants have the same issue.
    Thanks again Alexander

    1
    Comment actions Permalink
  • Avatar
    Chad Reitsma

    Fixed the same issue on all our Wordpress sites, can't download or update plugins without cURL! (error 77)  It would be nice if Plesk restarted these services automatically.

    2
    Comment actions Permalink
  • Avatar
    Tom Pel

    Always send out notifications and emails to all users for this kind of thing. You don't wait till my business is fucked and I google a solution before you start telling me one update caused a server error. What am I paying for? Improve on your customer relation. This really gave me a sleepless night changing what wasn't broken onmy site to no avail only to google search and I find this page telling me some server updates wasted my night. WTF, this is really annoying!

    1
    Comment actions Permalink
  • Avatar
    Unknown User (Edited )

    Unfortunately the error "Request Failed with a Fatal Error: Curl error: [77] ." is not resolved after restarting plesk-php* and sw-engine. Any other suggestions?

    Edit: Resolved! Since we are also running Litespeed we had to also restart lscgid

    0
    Comment actions Permalink
  • Avatar
    AP: G

    Hi,

    Can you confirm please if the "Event Handler" --- "Update Installed" is fired after the system updates are completed, and would be safe to run the above command without issue?

    0
    Comment actions Permalink
  • Avatar
    Enrico Venezia

    Really thank you, it solved the problem. You could also encounter different PHP CURL problems.

    0
    Comment actions Permalink
  • Avatar
    Anthony Ezeamaka

    This fixed the problem.. Thank you!

    0
    Comment actions Permalink
  • Avatar
    Aaron Crawford

    If anyone is getting errors such as 'Unit plesk-php.service' cannot be found, try wrapping the above command in quotes, e.g.:

    systemctl restart 'plesk-php*'
    0
    Comment actions Permalink
  • Avatar
    Alexandre Ribeiro

    That fixed the problem.. Thank you!

    0
    Comment actions Permalink
  • Avatar
    Marco Padovan (Edited )

    one some instance where there was some plesk-php versions installed but not running the restart of sw-enging was failing due to &&

    This so far blindly fixed them

    systemctl restart 'plesk-php*' ; systemctl restart sw-engine ; systemctl restart psa
    0
    Comment actions Permalink
  • Avatar
    mwgbr (Edited )

    Hi,

    thank you for the infos,

    we had to switch on/off ssh for the subscription to mitigate the issue, like explained in the following post.

    https://talk.plesk.com/threads/could-not-get-mozilla-tls-config-curl-error-77-cannot-update-plugin-et-al.371956/post-936719

    I think the real issue for us was:

    https://www.plesk.com/kb/support/on-plesk-for-linux-server-curl-command-in-chrooted-shell-or-in-scheduled-task-fails-curl-77-error-setting-certificate-verify-locations/

    Cheers!

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request