A
default installation of freevsd-1.4.10 will only allow secure connections on
port 1726 (you can do a netstat -nl on the hosting server to confirm this).
Currently the web-admin scripts operate by calling vsdadm raw_io to send raw
protocol requests out to a hosting server from the web-server. vsdadm (as
opposed to svsdadm) does not support SSL encryption and will therefore attempt
to connect to the hosting server on port 1725. It doesn't find any service,
hence the error message you describe. You must open up the hosting server
to listen for non-SSL encrypted vsd requests on port 1725. This can easily be
done by editing inetd/xinetd and adding/enabling an entry for vsd as opposed to
just svsd. Please note that for security you should then ensure that only
requests from your web-server are accepted - see the INSTALL document, 6.2.1 -
'Securing Remote Access to VSD'.
Tim
-----Original Message-----I've got the web admin scripts running and am able to authenticate with the database. It shows the virtual server associated with this account, when I click on administrate it goes to the Virtual Server Administration page, however, when I try to perform any administration functions at all it comes back with
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rob Secrist
Sent: 08 October 2001 20:02
To: [EMAIL PROTECTED]
Subject: Internal Error
Internal Error :
Communications Time Out.
The hosting server this virtual server is on may not be running, or
you have tried to make a connection to an invalid server.
If the hosting server is down, a Support Engineer has been paged.
Ideas?
This is running 1.4.10 on RedHat 6.2 with the web admin scripts that were included on the CD. Also, this machine is behind a BSD based firewall on a private lan. I shouldn't have to open up 1725 on the firewall should I?
Regards,
Rob-
