I have a domain with a SSL at https:/www.example.com.
I want that http://www.example.net shows the same website as example.com (same website folder).
I've tried with domain alias in Plesk but it's redirecting to https://www.example.com .
This question appears to be off-topic. The users who voted to close gave this specific reason:
There are multiple things to consider to get this setup to work (and I dont know how much of it plesk handles... We DO have a webmaster exchange site now, as far as i know).
1) Get domain2 to point to the webserver at domain1.
Either change the
2) Get a valid SSL certificate for domain2
You can't use the SSL certificate from domain1 for domain2. You can't do any kind of
3) Configure a means to differentiate between domain1 and domain2
When an SSL connection is made, ..traditionally Apache HTTPd must provide a copt of its certificate before any information is exchanged. At this point, the only thing Apache knows, is the remote IP and the local Apache IP and the relecant ports (and various other TCP headers that are largely unimportant to us). Because Apache knows nothing about the domain name that was used it must attempt to serve a valid certificate for an unknown domain (Apache's Strategy: Use the first one listed in the config).
SSL connections are generally made on port 443. So generally speaking, most external SSL connections to your website will come in on TCP port 443. The remote IP and port are chosen by the client, so in most cases, you can only control which IP the request comes to. Assigning separate IP addresses to domain1 and domain2 is the
Many people that have websites don't have the luxury of owning multiple IP addresses. The dirtiest and most
The solution that basically everyone uses is Server Name Indication (SNI). This is an extension to the TLS (See: SSL) protocol that essentially adds a Host: header to the request. Read about it here: http://en.wikipedia.org/wiki/Server_Name_Indication . The Relevant RFCs are listed in the sources if you care.
Plesk probably supports SNI but again, I don't play with plesk. Configuring SNI with plesk should be a googlable affair.
4) Create separate virtual hosts in apache for the domains
This is important because of the above SSL considerations. You can't simply use Apache's
I Never said I needed SSL on domain2!!!!!
Ok. Good news (If that is the case). Create a CNAME in the DNS for domain2 that points to Domain1. Just know that: You will lay awake at night wondering if users are ever typing: https://domain2.com into the address bar manually and seeing the SSL warning.
And finally, I'd love to give you specific Plesk instructions with screenshots, but I don't know Plesk and I think you (and anyone researching this in the future) might benefit more from a little fundamental knowledge on the backend operations than the point and click solutions. Good Luck. :)
In order to navigate to the DNS Editor in Plesk, please follow the instructions below:
To edit a CNAME Record:
After making your changes, click OK.