View Single Post
Old 18th November 2005, 19:34
falko falko is offline
Super Moderator
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,749 Times in 2,579 Posts

Originally Posted by phamels

I've been using ISPConfig since 2.08 and it's been working great ever since

I have 2 questions tough, one is about setting up SSL.
Everything is working perfect. I'm creating a new domain: domain.tld
This domain is bound to an unused and freshly added ip. This ip will be used entirely for this domain since it's going to use SSL.
When I activate SSL from the webinterface and create the certificate, I see a certificate coming up in de web_userxx/ssl dir.
When i try to connect to https://www.domain.tld using lynx, i get the following errors:
SSL error:self signed certificate-Continue? (y)
i continue...
SSL error:host(www.domain.tld)!=cert(localhost.localdo main)-Continue? (y)
i continue...

Then I see the page located in /var/www/index.html

This isn't very right, right ?
It seems there's a problem with creating the Certficate or something, don't really know much about SSL except I have to set it up lol
Does www.domain.tld point to the correct IP address? Can you see an SSL vhost for www.domain.tld in your Vhosts_ispconfig.conf?

Originally Posted by phamels
Next issue, can i forward a domain so i have domain1.tld and domain2.tld acting as 1 domain, for example: www.domain2.tld should point to www.domain1.tld, blah.domain2.tld should also point to blah.domain1.tld...
Is this possible ?
Yes, you can create the new domains as Co-Domains in the existing web. You can also work with the Forward feature of Co-Domains.
But please make sure the DNS records for the new domains are correct.

Originally Posted by phamels
also with SSL activated ?
Only if you have a wildcard SSL certificate. Normally an SSL certificate is for one FQDN only, any other combination will issue an error.
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!


nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote