Websites show 502 Bad Gateway after enabling nginx on a server with Fail2ban




  • Avatar
    Olosz Andor

    This solution is worked for me (Plesk 17.0.17)

    Thank you! :)

  • Avatar

    did not help

  • Avatar
    Pavel Mikhaylov

    Hello iamkingsleyf,

    Could you clarify a few moments, please:

    1. Did the symptoms match entirely to ones you were having? 502 error is quite general and solutions may vary, depending on the additional symptoms.
    2. Does the issue still persist or did you manage to resolve it by other means?

    If the issue is not resolved, I would like to recommend to contact our support:

  • Avatar
    Lok Ming Chu

    I have this problem in my server, The bug have not fixed.

    However, I add my server IP to trusted IP list, That is ok, now.

    Here is my server information

    OS CentOS Linux 7.4.1708 (Core)
    Product Plesk Onyx
    Version 17.5.3 Update #45, last updated on April 16, 2018 10:36 AM
  • Avatar
    Pavel Mikhaylov

    Hello Lok Ming Chu,

    As the article states:

    Note: Even if the latest micro update of Plesk 17.5 is installed, the issue may persist if fail2ban and IP addresses were configured on the server before 19 MU. In this case, apply the 1st and 2nd steps.

    If this is the case, you have applied the correct solution.


  • Avatar
    Parahoster / Thibaut Robert


    j'ai cette erreur
    Réorientation / bin / systemctl redémarrer iptables.service
    Job pour iptables.service a échoué parce que le processus de commande est sorti avec le code d'erreur. Voir « état systemctl iptables.service » et « journalctl -xe » pour plus de détails.

    I don't understand

  • Avatar
    Alisa Kasyanova

    @Parahoster / Thibaut Robert
    Such error means that iptables service was not restarted properly: it ended up in some error. Check the "service iptables status" output for more information on the cause

Please sign in to leave a comment.

Have more questions? Submit a request