Debian 8 upgrade - New websites not loading properly

9 posts / 0 new
Last post
#1 Fri, 10/09/2015 - 04:34
thesmahesh

Debian 8 upgrade - New websites not loading properly

Dear All,

I was running Debian 7 with Webmin version 1.770
Virtualmin version 4.18.gpl

Last night i upgraded to Debian 8 following the given below url

https://www.virtualmin.com/documentation/system/os/debian-wheezy-to-jess...

Everything went on fine.

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.

Thanks and Regards

Fri, 10/09/2015 - 08:23
thesmahesh

I checked the error logs. This is what i oberved.

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

Please help.

Thanks and Regards

Fri, 10/09/2015 - 09:01
thesmahesh

Another observation

If i use https://domain.com, it loads fine But, if i use http://domain.com, it loads the default website and not the intended website.

Please help. Thanks and Regards

Fri, 10/09/2015 - 09:14
thesmahesh

Another observation

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
Fri, 10/09/2015 - 09:33
andreychek

Howdy,

Having the default domain in there while Virtualmin created the new Virtual Server may have caused Virtualmin to use the wrong settings.

The "Any" address shown in your last post may be the source of the issue.

Take a peek at this document, this may help you get things working the way they should be:

https://www.virtualmin.com/documentation/web/troubleshooting#The_Wrong_S...

Fri, 10/09/2015 - 09:44
thesmahesh

Hello andreychek,

to quote from the link given above,

"You would also want to verify that each VirtualHost block lists an IP address, and not an asterisk (*) character."

That exactly is my issue

All new virtual servers created after debian 8 ugrade have the given below format, whereas the servers created before upgrade are perfectly fine.

/etc/apache2/sites-enabled/newdomain.com.conf:<VirtualHost *:80>

How do i resolve the same ?

Thanks and Regards

Fri, 10/09/2015 - 10:10
andreychek

Howdy,

You can just edit those files and change them to match the older ones.

Once you get rid of all the config files using the incorrect format, all new domains should be created correctly.

After making the changes, you'd need to restart Apache.

-Eric

Fri, 10/09/2015 - 10:21
thesmahesh

Hello andreychek,

Issue resolved. Thanks a lot,

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 ?

Thanks and Regards

Fri, 10/09/2015 - 11:09
andreychek

Howdy,

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.

I'm glad you got it working now though!

-Eric

Topic locked