How To ISP Server setup with Ubuntu 5.10 (Breezy Badger)

[gymsmoke]

I followed all of the steps here very carefully, save one. I went through the ispconfig installation with "standard" rather than "expert" mode. I'm hoping that this is the solution to the problem I'm having. Everything in the How To went very smoothly.
At the end. Since this is a test environment, the system has a hostname, but is setup as localhost.localdomain. After the completion of the install, I went to
"https://my_ip_address:81", and got this message (firefox 1.5)
"Could not establish an encrypted connection because certificate presented by 'my_ip_address' is invalid or corrupted. Error code: -8182 ...

Any input to this would be greatly appreciated. I'm sure I followed every step here quite carefully (with the noted exception above). This is my first server install, so I was really quite pleased with the progress I had made until this.

[falko]

Originally Posted by gymsmoke

"Could not establish an encrypted connection because certificate presented by 'my_ip_address' is invalid or corrupted. Error code: -8182 ...

You have a corrupt SSL certificate. Create a new one as outlined here: http://www.howtoforge.com/forums/sho...58&postcount=4

[gymsmoke]

fallko~
Thank you for the reply. That certainly helped. The keys now show up in the directory where they should have showed before (although for some reason I don't recall doing the steps you outlined as part of the how-to)...
Now, whether I use https://my_ip_address:81 or http , I get
"The connection was refused when attempting to contact my_ip_address:81"
the box is alive, and it can be ping-ed...
the logs don't have any strange entries in them, so according to the installation and setup, everything "looks" as though it went fine.

I appreciate your feedback.

[gymsmoke]

Falko~
I went back through all of my notes on the installation and found one deviation that I made - it seems relatively minor, but I'm wondering if this has anything to do with the problem of not being able to connect...
When installing ispconfig, i didn't choose "expert" mode. So, apache2 sees the doc root in /var/www , while ispconfig sees it in its default, which I believe is /home/www ...
/home/www is empty, and /var/www contains: apache2-default sharedip webalizer

Could this be the problem ?

[gymsmoke]

Falko~
ok... more good news. If I access the site by ip address (port 80), I get a directory listing as above (apache2-default sharedip webalizer). If I select apache2-default, I get the expected Apache default index.html . If I select sharedip, I get this:
"SharedIP"
This IP address is shared. For access to the web site which you look for, enter its address instead of its IP.
For questions or problems please contact the server administrator.
--------------------------------------
powered by ISPConfig

So, apparently I can see the server and at least get to the default page(s)...

It feels like a config problem to me.

[Parcye]

I am stuck in the same position. I have done a re-install, but still get stuck in the same position.

If I use lynx to view ispconfig on the ispconfig machine, I get want I want to see.

[falko]

Originally Posted by gymsmoke

fallko~
Thank you for the reply. That certainly helped. The keys now show up in the directory where they should have showed before (although for some reason I don't recall doing the steps you outlined as part of the how-to)...

The original certificate was generated during the ISPConfig installation. I guess you entered wrong values there.

Originally Posted by gymsmoke

Now, whether I use https://my_ip_address:81 or http , I get
"The connection was refused when attempting to contact my_ip_address:81"
the box is alive, and it can be ping-ed...
the logs don't have any strange entries in them, so according to the installation and setup, everything "looks" as though it went fine.

Please post the output of

netstat -tap

Also make sure that no firewall blocks port 81.

[falko]

Originally Posted by Parcye

If I use lynx to view ispconfig on the ispconfig machine, I get want I want to see.

Then I guess it's a firewall problem. Make sure your firewall doesn't block port 81.
Is your ISPConfig system inside a LAN, and you're trying to access it from the outside? Then the problem could be that some providers block port 81.

[gymsmoke]

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 localhost.localdo:mysql *:* LISTEN 7901/mysqld
tcp 0 0 *:ftp *:* LISTEN 14588/proftpd: (acc
tcp 0 0 216.215.55.21:domain *:* LISTEN 14574/named
tcp 0 0 localhost.locald:domain *:* LISTEN 14574/named
tcp 0 0 localhost.localdoma:953 *:* LISTEN 14574/named
tcp 0 0 *:smtp *:* LISTEN 14544/master
tcp6 0 0 *:imaps *:* LISTEN 9520/couriertcpd
tcp6 0 0 *op3s *:* LISTEN 9423/couriertcpd
tcp6 0 0 *op3 *:* LISTEN 9360/couriertcpd
tcp6 0 0 *:imap2 *:* LISTEN 9465/couriertcpd
tcp6 0 0 *:www *:* LISTEN 22114/apache2
tcp6 0 0 *:ssh *:* LISTEN 6915/sshd
tcp6 0 0 ip6-localhost:953 *:* LISTEN 14574/named
tcp6 0 0 *:https *:* LISTEN 22114/apache2
tcp6 0 352 ::ffff:216.215.55.2:ssh ::ffff:209.208.34:50709 ESTABLISHED21892/sshd: gymsmoke

[falko]

ISPConfig isn't running at all. Please start it:

/etc/init.d/ispconfig_server start