Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

curl shows error on Plesk server: Could not resolve host: example.com: Name or service not known

Follow

Comments

12 comments

  • Avatar
    H.W. Bartels

    Thank you. I had the same problem, but that was after Plesk updated the CENTOS. 

    It would be nice when updates through Plesk of the OS (CENTOS) automatically restarted the updated services

    Henk

    1
    Comment actions Permalink
  • Avatar
    Miha Gregorš

    Hi,

    I agree with Henk. It would be nice when Plesk update CentOS packages, that automatically restarted the updated services and services which uses files of updated packages.

    Regards, Miha

    0
    Comment actions Permalink
  • Avatar
    Gianluca

    "H.W. Bartels" i agree, Plesk should restart automatically the updated services when certain updates of the OS through Plesk require a restart of these services.

    0
    Comment actions Permalink
  • Avatar
    JL Detan

    Hi! i restarted the FPM service, Apache and Nginx via PLESK, but still not working for me, I try to put a lets encrypt certificate to a new domain and says this:

     

    Error: Could not issue a Let's Encrypt SSL/TLS certificate for tombrownsmagaluf.com.
    Details

    Could not obtain directory: cURL error 6: Could not resolve host: acme-v01.api.letsencrypt.org; Name or service not known (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
     
    any help please?
    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Miha, @Gianluca!

    Currently, the optimal solution is under consideration. 

    Click "Follow" to be notified when this article will be updated.

    0
    Comment actions Permalink
  • Avatar
    Denis Bykov

    @JL Detan

    It should work now. Such issues were caused by planned maintenance of Let's Encrypt server side. Check out this article for more info - https://support.plesk.com/hc/en-us/articles/115004456013

    0
    Comment actions Permalink
  • Avatar
    Alan Melnikov

    Me gustaria sabre si Funciona la solucion, ya Que ya indicados reinicie Servicios los, Menos el Servidor

    ¿Es necesario reiniciar el servidor completamente?

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Alan, usually it is enough to restart services listed in the article only.

    However, we have already met cases when only server restart resolved the issue completely.

    Please, restart the server and let us know if the issue persists.

    0
    Comment actions Permalink
  • Avatar
    JL Detan

    Hi, for me worked restarting the server, now all works fine, thanks

    1
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @JL Detan, glad to know that the issue is resolved.

    0
    Comment actions Permalink
  • Avatar
    Alan Melnikov

    Buenas tardes, he resuelto mi problema, Hice clic en el botón 'Reiniciar' para cada servicio FPM, Apache y Nginx:, no hubo necesidad de reiniciar el server, y la licencia respondió bien, agradezco el aporte y la orientación al mismo.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello @Alan, glad to know that the article helped and no server restart was required in your case.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request