Installed Perfect Server for Hardy Heron 8.04 from this guide: http://www.howtoforge.com/perfect-server-ubuntu8.04-lts Installed ISP Config from this guide: http://www.ispconfig.org/manual_installation.htm Now when I access the ISPConfig page from 192.168.2.11:81 i can't get past the login page without a "ERROR 101: wrong username or password." when I try to enter the default admin admin Same thing from localhost:81 I can't access the page with the recommended http://www.xyz.de:81 (which is the default host name and domain used for the install). I have tried to reinstall over the initial installation which only made it worse because then I couldn't even browse to the login page. I uninstalled ISPConfig and reinstalled with the original resulting error message. The only thing I know I missed is in the last section of the ISPConfig guide when it advises the proper course of action for dealing with quota, the referenced "/home" file does not exist in my copy of /etc/fstab so I am not able to apply the advised edit. netstat -tap output root@server1:/home/sysop/Desktop/install_ispconfig# netstat -tap Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 *:mysql *:* LISTEN 6930/mysqld tcp 0 0 *:www *:* LISTEN 6005/apache2 tcp 0 0 *:81 *:* LISTEN 29675/ispconfig_htt tcp 0 0 server1.example.:domain *:* LISTEN 5101/named tcp 0 0 localhost.locald:domain *:* LISTEN 5101/named tcp 0 0 localhost.localdoma:ipp *:* LISTEN 5456/cupsd tcp 0 0 *:smtp *:* LISTEN 29579/master tcp 0 0 localhost.localdoma:953 *:* LISTEN 5101/named tcp 0 0 *:https *:* LISTEN 6005/apache2 tcp 0 0 server1.example.com:81 server1.example.c:39316 TIME_WAIT - tcp6 0 0 [::]:imaps [::]:* LISTEN 5389/couriertcpd tcp6 0 0 [::]op3s [::]:* LISTEN 5429/couriertcpd tcp6 0 0 [::]op3 [::]:* LISTEN 5406/couriertcpd tcp6 0 0 [::]:imap2 [::]:* LISTEN 5365/couriertcpd tcp6 0 0 [::]:ftp [::]:* LISTEN 29622/proftpd: (acc tcp6 0 0 [::]:domain [::]:* LISTEN 5101/named tcp6 0 0 [::]:ssh [::]:* LISTEN 5126/sshd tcp6 0 0 [::]:smtp [::]:* LISTEN 29579/master tcp6 0 0 ip6-localhost:953 [::]:* LISTEN 5101/named root@server1:/home/sysop/Desktop/install_ispconfig# I checked my config.inc.php file but don't see anything obvious in there. hosts file: 127.0.0.1 localhost.localdomain localhost 192.168.2.11 server1.example.com server1 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts I'm almost positive that something of this nature must be a simple fix - something I've missed along the way. Any help would be greatly appreciated - I'm on a very steep learning curve here.
Did you see any errors during ISPConfig installation? Can you check (e.g. with phpMyAdmin) that the ISPConfig database exists and that it is not empty?
Thanks for the quick reply falko. I don't recall seeing any errors during install. I also don't see any sign of an ISPConfig database when I use phpMyAdmin. Admittedly, I'm not sure if I'm looking in the correct place though.
Ok, that's a big problem. What's the output of Code: df -h ? Do you see any warnings/errors in the ISPConfig installation log in the /var/log directory?
Output of df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 71G 3.0G 65G 5% / varrun 1.5G 144K 1.5G 1% /var/run varlock 1.5G 0 1.5G 0% /var/lock udev 1.5G 44K 1.5G 1% /dev devshm 1.5G 12K 1.5G 1% /dev/shm lrm 1.5G 40M 1.4G 3% /lib/modules/2.6.24-24-generic/volatile I found these warnings: Fri Jun 12 14:59:21 CDT 2009 - [ISPConfig] - /home/sysop/Desktop/install_ispconfig/install.php, Line 794: WARNING: could not dump old db to file existing_db.sql Fri Jun 12 14:59:21 CDT 2009 - [ISPConfig] - /home/sysop/Desktop/install_ispconfig/install.php, Line 808: WARNING: could not read in db_ispconfig.sql Fri Jun 12 14:59:21 CDT 2009 - [ISPConfig] - /home/sysop/Desktop/install_ispconfig/install.php, Line 815: WARNING: could not import existing_db.sql
Ok, there really was a problem with the database during installation, but I can't say why. At least disk space was no issue...
