Now all my websites which were created before upgrade are working perfectly fine.
But when i create a new virtual server, it loads my default website and not the correct one.
I tried a2dissite default
But no resolution.
Looks strange to me.
Please help me resolve the issue.
Cannot serve directory /home/domain/public_html/: No matching DirectoryIndex (index.html,index.htm,index.php,index.php4,index.php5) found, and server-generated directory index forbidden by Options directive
Type Address Port Server Name Document Root
Virtual Server ipnumber:80 Any old-domain.com /home/old-domain.com/public_html
Virtual Server ipnumber:443 Any old-domain.com /home/old-domain.com/public_html
Type Address Port Server Name Document Root
Virtual Server Any 80 newdomain.com /home/newdomain.com/public_html
Virtual Server ipnumber:443 Any newdomain.com /home/newdomain.com/public_html
Can you please let me know why in the earlier case with incorrect format (*.80), it was getting directed to the default domain whereas with https (ipnumber:443), it was loading fine ?
It’s what I mentioned in my comment above, that having the default domain (which you already removed) in there while Virtualmin created the new Virtual Server caused Virtualmin to use the wrong settings.
That default domain was using *:80, which caused Virtualmin to think you wanted all new domains to use that format.