Using automated tasking of Virtualmin, I moved two websites from shared hosting (TopWeb) to VPS (TopServer). After the DNS propagation of the first website was completed, the website is properly visible and typing the TopServer address in the address bar of the browser, at that moment, you can see a “Not found” page. Instead, after the DNS propagation of the second website was completed, the website is properly visible, but typing the TopServer address in the address bar of the browser, at this time, you can see the homepage of this second website, instead of “Not found” page as before. Is it normal? If so, if I should add a third website to TopServer and I should type its address in the address bar of the browser, I will see the homepage of this third website? If it isn’t normal, how can I fix this issue? By the way, where can I find the “Not found” page in the system? Thank you.
I’m not sure I fully understand the problem here… Can you please re-iterate the present situation after your move to a VPS, which domain name shows correctly and which does not?
What exactly do you mean with “Not found page”? If you mean the stuff your browser displays for a 404 or other server error: You can configure those for existing domains under “Services / Configure Website / Error Handling”. If I recall correctly, there should also be a way to configure that for new domains in a template. Can’t recall where that was though, if I do I’ll add the info here.
Locutus, thank you. I fix the issue reading “Default website on IP” at this address: https://www.virtualmin.com/node/11906 .
I think this behavior must be changed in Virtualmin server, in order to avoid the penalties of Google relatively to duplicate websites. In fact, with the default situation of the Virtualmin server the same contents are shown on two domain names: that of the server and that of the website.
Actually, there’s not much that Virtualmin can actively do against that. When Apache receives a request, it will serve it, preferably from the domain that is requested. But if the request is for a domain that it doesn’t know, it will serve it from the alphabetically first domain in its configuration.
If you wish to avoid having a certain domain being served for the server’s hostname (or IP address for that matter), you need to create a “dummy” domain and assign it as the “default for this IP”, just like you did.