1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

firewall lock - out and Plesk start problem

Discussion in 'Plesk for Linux - 8.x and Older' started by placebo, Jan 23, 2005.

  1. placebo

    placebo Guest


    I am in desperate need of some help.

    I am running Suse 9.1, Apache webserver and Plesk 7.5 Reloaded.

    I have misconfigured the firewall, so it blocks ssh on my server. The idea was to secure the server and before going by ssh on the server disable the firewall rule in PLesk Admin Panel..

    For some reason - I did not find out why yet, Plesk does not start when the system is rebooted and I am facing the following problem:

    No Plesk available, so no login, no firewall change possible via Plesk and therefore no ssh.

    So I locked myself out of the server accidentally.

    I can manage to get on the server via rescue system however but I need a hint:

    Can somebody tell me, in which directory and in which file the iprules of Plesk Firewall are stored, so I can browse there and delete the line blocking my access to ssh?

    Or any other good idea what I can do, if I only have rescue system access to my server?

    Yes, I know - stupid mistake with blocking ssh - at the same time bad luck that plesk don't work anymore.

    Please help, but speak easy language - I am new to Linux systems. ;)

    Thank you.
  2. Cranky

    Cranky Guest

    You can simply stop iptables ... service iptables stop (in redhat). Rules are stored in /etc/sysconfig/iptables in redhat.