Hello! I've recently installed ISPConfig 3.1.2 on a fresh ubuntu 16.04 installation using the automatic tool. I've created a first website/db/ftp and uploaded the content successfully using the system. Now when I try to create a new website to the same customer, even though it has it's own DNS entries inside ISPCONFIG and it's own directories, When trying to enter the website I see the first website. You can see the problem here: http://seaview17.com (redirects to https://emd.diamonds even though there is no redirection configured). Will be glad to get your help.. Thank you.
Anyone? Please help me. when trying to curl this domain using my PC I get a short HTML page which says this domain is being 302 redirected to emd.diamonds. There is no .htaccess file on the virtualhost's web root, and all Apache's settings were created automatically by ISPConfig. What could be the problem ? Thank you, Tzahi.
I can confirm the 302 redirect. Is there anything under the Redirect tab for the seaview17.com website?
The above example is no longer relevant. I've changed the domain to point now to another server until I'll fix the problem. (seaview17.com). There is nothing under the Redirect tab on the seaview17.com website. another thing is, that I have a .htaccess file on the emd.diamonds website (client1/web1) which supposed to change the address of each client to "https://emd.website". When I removes that .htaccess from emd.website - the result is that entering seaview17.com shows the content of client1/web1 (emd.diamonds) and the URI is still seaview17.com (without redirection, just shows the content of another directory) Will be glad for any help. it happens on all new websites I open in ISPConfig. (there all takes the data of any virtualhost from client1/web1/. Thank you!
That sounds like you've mixed ip addresses among your sites, eg. web1 site has the ip address set, while other sites have '*' as the ip address - you want to consistenly use one or the other. That doesn't explain the redirect you used to have, but maybe gets you closer to working.
Thank you very much @Jesse Norell , that was the problem. The redirection happent because on web1 I have an htaccess file that redirect all regular traffic to https://. so requesting http://seaview17.com made a redirection to https://emd.diamonds. Can you please shortly explain to me why not specifying the server's ip address routed all traffic to web1? I'm trying to understand the system's logic. Thank you very much! you've helped me a lot.
It's the order in which the web server matches the request to available virtualhost definitions, explained in https://httpd.apache.org/docs/2.4/mod/core.html#virtualhost
