Hello, sushko, you wrote: S>> Yes, still such thought: and SNI normally works? S> I do not know that this such. To Vick esteemed on this subject, but plainly understood nothing. It is such libraries and SSL protocol that it was possible on one IP and to port to hold some HTTPS-sites. Demands support both on server side, and on client side. By rules, the client is knocked on 443 port, on it one HTTPS-site hangs, there is an exchange of certificates-keys - and all works. If to do SNI the client is knocked on 443 and asks to give it the necessary sert/key, then the client is once again knocked. A counter that at such circuit the client at first tries to come on the first site described in a config of the Apache, and, if at it a problem with there will be problems with all who on this server lives. At such circuit crookedly tuned server can on HTTP give the necessary site, and on HTTPS - what you costs to the first in a config, accordingly.htaccess htaccess, especially regarding a redirect on HTTP, it will be sent by wood. The server or a hosting? Broad gulls and global adjustments of the Apache can look?