Firewall Blocks all...

Hi,

I have followed this tutorial:
http://www.howtoforge.com/perfect-server-ubuntu-12.04-lts-apache2-bind-dovecot-ispconfig-3

and all worked fine.
I added dropbox and TS3, with separate users that run the programs.
However, after several restarts of the server, suddenly all ports are blocked and I can't access the server in any way anymore.

Any idea how that can come to pass?

Best regards,
Heinrich K.

 

Check the status of ufw

 

What's "ufw" ?

In any case, I had to call my hoster so the server was reset completely, since I could not log in via ssh anymore, or do anything, for that matter...

After it happened for a second time, I changed to an hoster provided image with ubuntu + plesk.

But actually I'd like to use the ISPConfig3 setup provided in the tutorial, but if I can't log in from one moment to another, it is kind of pointless....

 

ufw is a program for managing a netfilter firewall

It means that after restart the "ssh" service is not start -up boot.

Add it in startup as

 

The ssh demon was in the start, as was apache, and dovecot and so on. Like I said, the server worked seemingly fine - as with the tutorial above.

However, without any reason (at least none I could find) the server had all ports closed after a 'reboot' command.

No, apache, no dovecot and no ssh.

My hoster provides a rescue system, which I then booted, and logged in to, but I could not find anything odd.

Since this happened twice - every time after I had set up the server, created profiles and so on, I though maybe it is a known phenomenon.

 

It means that the firewall gets started with the reboot

use

& then chek the status after restart

 

Would there be a way to achieve that, from the rescue system?

Meaning, if I only have access to the file system, where would I make sure the firewall isn't loaded ?

And why would the firewall activate itself anyways. It didn't all these reboots before...
And the tutorial clearly status, that ISPConfig3 comes with it's own firewall.

 

UFW is prenative firewall with a debian/ubuntu. It is always in deny mode by default But sometimes it gets activated may be due to some installations, so better to either remove or de-activate ufw.

To deactivate it you can use

as

 

Thanks for the info.

I'll retry to setup the server with this in mind later this month...