• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Recent content by aernative

  1. A

    Resolved 502 Bad gateway with "Let's Encrypt" domain

    Solved this now. Had some entries in the - Apache & nginx Settings settings - specifically - Additional directives for HTTPS SSLEngine on SSLProtocol all -SSLv2 -SSLv3 SSLHonorCipherOrder on SSLCipherSuite "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256...
  2. A

    Resolved 502 Bad gateway with "Let's Encrypt" domain

    Now looks like this is a problem with one domain only - our main domain, cant enable letsencrypt for that domain without all the others returning bad gateway! Very frustrating.... no idea where to look...
  3. A

    Resolved 502 Bad gateway with "Let's Encrypt" domain

    OK - I've now found more info - I also get 502 Gateway issues if one of the domains secured by letsencrypt is also the same domain used by plesk admin - as soon as you do this all the domains are 502 except the domain matching the control panel domain. The only way I can get around this is to...
  4. A

    Resolved 502 Bad gateway with "Let's Encrypt" domain

    Nopte - solved this - i dont know why - if you have a domain with your own SSL certificate and you later add more domains and use LetsEncrypt that is the problem - it appears if your using letsencrypt *you have to use that software will all domains* requiring SSL presently as otherwise you may...
  5. A

    Resolved 502 Bad gateway with "Let's Encrypt" domain

    Having seem similar issue https://talk.plesk.com/threads/letsencrypt.339350/ tried installing the last patches again - plesk installer --select-release-current --reinstall-patch --upgrade-installed-components No difference - still getting bad gateway. Also - I do have a domain with a regular...
  6. A

    Resolved 502 Bad gateway with "Let's Encrypt" domain

    Have followed all the suggestions I can find regarding this but nothing is sorting the problem. Essentially - wordpress site (weather that has anything to do with it i dont know...) - PHP settings/apache settings - no combination makes any difference... Still get the same in the error log -...
Back
Top