ISPConfig 3 Not Following Path - Bad SSL

Discussion in 'General' started by midcarolina, Jan 17, 2012.

  1. midcarolina

    midcarolina New Member

    Hello,

    Not sure if anyone is having this problem too. I have reinstalled Fedora 14 x86_64 on a new server and added just 6 LAN IPs, starting with:

    192.168.11.245 to 250

    ISPConfig will not not only not follow the path to the file manager (loaded through FTP), but SSL Certificates aren't valid. The vhost shows the correct file path to /sites-enabled/ but won't launch the site, and now the SSL that I generated and is verified by Starfield Technologies (through GoDaddy) cert and bundle aren't acknowledged. Thee SSL error is

    Untrusted...generated by localhost.localdomain (indicating that ISPConfig is disregarded) I tried using the first IP ending in 245. Restarting Apache shows that a vhost has to be generated and that an SSL has been created for this specific IP as well. Here is an Apache restart (NOTE that port 80 and 443 are not listed anymore for 245).

    No need to post ifconfig or ifconfig -a as it shows these same available IPs. This stinks as I can not only not launch the site but cant create SSLs for clients!


    Starting httpd: [Mon Jan 16 15:49:59 2012] [warn] NameVirtualHost 192.168.11.247:80 has no VirtualHosts
    [Mon Jan 16 15:49:59 2012] [warn] NameVirtualHost 192.168.11.247:443 has no VirtualHosts
    [Mon Jan 16 15:49:59 2012] [warn] NameVirtualHost 192.168.11.246:80 has no VirtualHosts
    [Mon Jan 16 15:49:59 2012] [warn] NameVirtualHost 192.168.11.246:443 has no VirtualHosts
    [Mon Jan 16 15:49:59 2012] [warn] NameVirtualHost 192.168.11.250:80 has no VirtualHosts
    [Mon Jan 16 15:49:59 2012] [warn] NameVirtualHost 192.168.11.250:443 has no VirtualHosts
    [Mon Jan 16 15:49:59 2012] [warn] NameVirtualHost 192.168.11.249:80 has no VirtualHosts
    [Mon Jan 16 15:49:59 2012] [warn] NameVirtualHost 192.168.11.249:443 has no VirtualHosts
    [Mon Jan 16 15:49:59 2012] [warn] NameVirtualHost 192.168.11.248:80 has no VirtualHosts
    [Mon Jan 16 15:49:59 2012] [warn] NameVirtualHost 192.168.11.248:443 has no VirtualHosts
    [Mon Jan 16 15:49:59 2012] [warn] NameVirtualHost *:80 has no VirtualHosts
    [ OK ]

    Thanks.
     
  2. jjone

    jjone New Member

    im having the same problem. i have a dedicated ip assigned to a website and installed godaddy SSL certificate, however when i access by the website https, the SSL is assigned by localhost not godaddy.

    i know it is a problem in ssl.conf

    i tried to comment out <vhost _default_:443> in ssl.conf but httpd will fail to re-start.

    did you figure out ?. please let me know. thanks.
     
  3. midcarolina

    midcarolina New Member

    SSL Issue with ISPConfig 3

    Hi jjone,

    I did figure this out (to a degree). Without giving me the exact IPs, can you describe your network set-up? A WAN IP to router (used as dedicated ip) with multiple LAN IPs? All details will help.
     
  4. jjone

    jjone New Member

    Hi, midcarolina
    i have a very simple network setup. no router and wire is connected direct to FIOS via a simple switch.
    i have 2 static ips for this server, eth0 and eth1. i can access both ips without problem. http is working for both ips.

    HTTPS is not working, it always load default SSL generated by my localhost. i installed a goddady ssl for 1 website with static ip in ispconfig 3. i double checked that my godaddy ssl is corrected installed in /etc/httpd/conf/sites-enabled

    im running centos 6.2. i tried to comment out the default localhost ssl found in /etc/httpd/conf.d/ssl.conf
    but httpd always failed to restart.

    any solution ? please help me. thank you.
     
  5. midcarolina

    midcarolina New Member

    Ok, this much I can say. Since CentOS is very similar to my distro, Fedora, I know that this could help. I am not 100%, but I feel it is a good possibility. If you are running eth0 and eth1 (which I did) this seems to cause problems.

    So I am assuming that one WAN IP is running the server to say, eth0? Then you did an add-on ip to the system inside ISPConfig first? I would try to eliminate the eth1 and change the network to read eth0 and eth0:0, with eth0:0 cloning eth0 NIC info but changing the ips and the ifcfg file name to ifcfg-eth0:0.

    Command (as root)

    # cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth0:0

    next,

    # vi /etc/sysconfig/network-scripts/ifcfg-eth0:0 and edit the content of the file

    # service network restart or # /etc/init.d/network restart
     

Share This Page