Discussion in 'General' started by mystix, Oct 5, 2005.
how a user can access his new website if the domain is not yet activ?
thank you for your help
If it is the first website for this IP, he can access the site with the IP.
If not, the only solution might be that you add temporarily a co-domain to that site
that already points to this IP. E.g. make some temp domains like temp1.yourcompany.com ..... temp10.yourcompany.com that points your server. If you get a new customer he can
access his site with this domain until his real domain is registered.
Do you think it's possible to add a URL like username.mylittlecompany.lu or userdomain.mylittlecompany.lu by default if a new webaccount is created?
Yes, but you must change the php code in the function that is called when a website is added. Or you post it to feature requests
I'm interested in this but I'm not sure exactly what has to be done...
if I've got web2 & web3, I should be able to create
web2.example.com, web3.example.com etc and just point to the servers IP ?
How do I access web2's website via a sub-domain of web1 ?
I should also note the reason I'm asking is for the ability to create a shared-ssl...
You mean web1 is www.example.com with the Co-Domain example.com?
You can then create a second web site web2.example.com in ISPConfig, and after you've saved that web site, you go to web2's Co-Domain tab and delete the example.com entry (with empty host), as it would conflict with web1's example.com Co-Domain.
Afterwards, all you have to do is create the appropriate DNS records (i.e., make web2.example.com point to your server's IP address).
Thanks that works nicely for http requests, but when I go to the same site via https it display's example.com (web1) instead of web2
Any insight to what's going on here ?
Much appreciated, Thanks!!!
Did you create an SSL web for web1 in ISPConfig before?
yeah, I had the ssl cert installed prior to creating web2 as a sub-domain...
That's why you see web1 when you use https.
Separate names with a comma.