I've manage to install Debian following the whole perfect Debian 3.1 manual. After initiating eBox installation, in the "Running A File-, Print-, Proxy-, DHCP-, AND Time-Server For Small/Medium Enterprises" it says "You will be asked a few questions. Most of the time you can simply accept the default values:", now the following questions never apeared on the screen: Code: Where should the PostgreSQL database be created? <-- /var/lib/postgres/data Should the data be purged as well as the package files? <-- No What locale should be used by the database backend? <-- en_US Choose European or US day/month order in dates. <-- European / US [depends on where you come from] DNS domain name: <-- example.com Name of your organization: <-- example.com Admin password: <-- somepassword Confirm password: <-- somepassword Allow LDAPv2 protocol? <-- No Enable suExec? <-- No Which paper size should be the system default? <-- a4 Use password encryption? <-- Yes Modify smb.conf to use WINS settings from DHCP? <-- No How do you want to run Samba? <-- daemons Create samba password database, /var/lib/samba/passdb.tdb? <-- No database requires login <-- No make configuration readable/writeable by owner only <-- No nsswitch.conf is not managed automatically <-- Ok Send daily reminders to users over quota <-- No and this was the very last line I saw Code: Setting up ebox-firewall (0.7.1) ... then SSH was dropped. Now, I can not access the server neither via SSH nor via web https://192.168.0.100, when I try the web access I got the following error: "192.168.0.100 has sent an incorrect or unexpected message. Error Code: -12263" Was following the whole perfect Debian 3.1 manual mistake? Should I just follow first 2 pages as sugested in the "Running A File-, Print-, Proxy-, DHCP-, AND Time-Server For Small/Medium Enterprises"? Is it possible to run ISPConfig and File, Print, Proxy, DHCP and Time Server on the same machine? Please help
That'S the normal behaviour. The eBox firewall blocks port 22. You can open that port using eBox' web interface. That's strange. Do you have physical access to the machine? Then you can log in using the normal terminal and try to fix the system. I haven't tested it, but it should work, I think.
