ISPConfig uses Localhost settings, VHosts instead through Apache Directive

Discussion in 'Installation/Configuration' started by Nap, Jul 16, 2012.

  1. Nap

    Nap Member

    I'm trying to make the ISPConfig page available to my clients via their own domain name. So far I've been able to do it, but not as elegantly as I would like.

    If they use the correct url, https://mydomain:ISPConfig_Port, it works fine. However, if they forget to enter the 's' and type http://mydomain:ISPConfig_Port Apache returns an error. Which is exactly what I want. (Not looking for a redirect here. They just gotta get it right.)

    However, in the error page, I get references to [email protected] (as ServerAdmin) and the (ServerName) as links within the error message.

    After investigation, I realised there is only one virtualhost entry for the ISPConfig in sites-enabled, and though the various domain names I'm hosting all work (they point to the same machine) the daemon is owned by the localhost. Hence my clients see the localhost address instead of their own.

    I am thinking that I could change that behaviour by putting a virtualhost entry into the Apache Directives for ISPConfig in each of the client's domain options page and setting the server parameters this way.

    Has anyone done this in their install?

    For the moment, I'm just going to change the error messages to not mention emails and domains.

  2. till

    till Super Moderator Staff Member ISPConfig Developer

    You are mixing up port based and namebased vhosts here. The ispconfig vhost is a port based vhost and not a namebesed vhost, for a port based vhost, there exists only one for all domains and not one for every domain. The port based vhost uses the fqdn server name (and not localhost) as hostname. If your server sues localhost, then you entered a wrong hostname during server installation.

Share This Page