Attempting to set up SSL site...
Posted: Tue Dec 17, 2013 2:52 pm
So, I have SSL all set up nicely and the like.
Then I visit the website, first via domain.com and not https://domain.com
All looks good... right up until I visit https://domain.com
The https://domain.com has the default Vesta Coming Soon site... at least up until I removed the default index.html.
Now... it didn't take me long to realize that VestaCP for whatever reason has chosen to explicitly set public_html as non-SSL and public_shtml as SSL and serve contents separately.
This is not how I'd prefer it to be, as in cPanel, you didn't have to worry about whether or not the domain would duplicate content due to it being served separately.
Now, I moved the non-SSL site over to the SSL area and all works well... but there is one issue. I tried to throw in a .htaccess rewrite rule which forces anyone visiting the site in question over to the SSL version as a way of working around the issue... no go.
So I thought about symbolically linking public_shtml to public_html. Any specific suggestions for that?
Edit: I would prefer to not have to worry about whether one area is more updated than the other and whatnot. I'd just prefer to have both non-SSL and SSL to be served from the exact same place: public_html
Then I visit the website, first via domain.com and not https://domain.com
All looks good... right up until I visit https://domain.com
The https://domain.com has the default Vesta Coming Soon site... at least up until I removed the default index.html.
Now... it didn't take me long to realize that VestaCP for whatever reason has chosen to explicitly set public_html as non-SSL and public_shtml as SSL and serve contents separately.
This is not how I'd prefer it to be, as in cPanel, you didn't have to worry about whether or not the domain would duplicate content due to it being served separately.
Now, I moved the non-SSL site over to the SSL area and all works well... but there is one issue. I tried to throw in a .htaccess rewrite rule which forces anyone visiting the site in question over to the SSL version as a way of working around the issue... no go.
So I thought about symbolically linking public_shtml to public_html. Any specific suggestions for that?
Edit: I would prefer to not have to worry about whether one area is more updated than the other and whatnot. I'd just prefer to have both non-SSL and SSL to be served from the exact same place: public_html