question about virtual domains

why does this happen, when i go to a domain that has no html file to it. it loads phpmyadmin by default?

if u go to https://wp.homelinux.com it will open phpmyadmin but if u go to http://wp.homelinux.com it brings up the right website.
the thing is that phpmyadmin is in diffrent users and diffrent domain.
if do mail.wp.homelinux.com it will do that same thing.
the file are in different directories.

Also, how can make so i can use ssl on more then one website. i have one of them but when i try do for another one it says it aready on that ip address?

and is there anyway that i can change the default way the email accounts are made up… i dont want them to be email_account.domain_user but i wanted them to be email_account@domain.

Shane

is your box called something.homelinux.com and it uses dyndns nameservers to point to your non-static IP ? and you want ssl and email too? Isn’t homelinux.com owned by Dyndns? Per haps a starting point would be their control panel I’m guessing

Anyway i dont think Im skilled enough to provide any sane answers here
except that for every ssl site you need a dedicated IP normally and email_account@domain can be set in the server template.

SSL requires static IP’s – Dyndns will not do this because your are using Dyndns dns which is forwarded to your dynamic IP.

Ok
I understand that…but im doing this on my server that is on private lan. but if say it needs a static ip address…the server is using a DHCP address…

everything works on there server but i cannot assign port 443 to more then on website.

where in the template can i change the users for the email?

shane

email: server template-mail for domain- at the bottom

for every ssl (port 443) you will need a static IP which you dont have
so
1 shared IP for regular domains and
1 dedicated IP per every ssl domain this means 10 websites with ssl is 10 static IP’s

if you have 1 domain and want ssl then you can try to make a folder, in the same level as public_html, called https and point the ssl DocumentRoot to that folder in Apache module.

ok…
I get it now… i made virtual ip address up for that and it worked…
what i need to know now is how can i make so when they go to that http it will redirect them to the https site…

might be able to do it with redirect pointer in dns? or something like that?
shane

Google has tons of answers to force http to https. Even the apache docs has that info.

why redirect at all?
for the first domain you can use http:// and https://
where http:// is located inside the public_html folder and the https:// is located inside the https folder you have created

just set the DocumentRoot of the ssl server to that https folder.
If you have enabled ssl then under webmins apache server module you will see 2 apache instances/webservers, 1 is port 80, the other on port 443

voila phpadmin can be installed in the https folder and your main site in the public_html cause i think that is what you wanted in your first post?

ok…
I have never done this before…so can u show me how to do this…or point me in a right direction…

because what i want to do is have virtual site off of the main one with out making new domain and dns and everything…

I have sub-servers now but i don’t to have that way because i just want to have to servers that are https:
right now i am doing this as a test, so i can implement it on a production server.

Shane

because what i want to do is have virtual site off of the main one with out making new domain and dns and everything..

I have sub-servers now but i don’t to have that way because i just want to have to servers that are https:
right now i am doing this as a test, so i can implement it on a production server.

I’m not sure I understand what you’re trying to accomplish…it sounds like maybe you’re making things way more complicated than is necessary.

If you want SSL, just turn on SSL for the domain that you’d like to have SSL on. You need one IP for each SSL virtual server. If you’re on a private network, you need one public IP for each SSL virtual server and they have to be port forwarding to the private IPs on which the SSL sites are running.

<code>
RewriteEngine On
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^(.*) https://%{SERVER_NAME}/$1 [L,R]
<code>

There are other ways including using php to rewrite the header location.

All depends on how you want it done.