I had to restore a backup since I screwed up with something, but now my the rewrite of "www.mydomain.com" to "mydomain.com" no longer works which means that I just land in some standard directory showing "Welcome to your new website". This also means that redirecting from "http://www.mydomain.com" => "https://mydomain.com" doesn't work either. All is set in the settings in ISPconfig, the cerificate is valid because when I go directly to "https://mydomain.com" it works as supposed to. It's a WP site.I have resynched ISPC3 /var/log/apache2/other_vhosts_access.log doesn't give me any hints either. Any hints of what I can do?
Have a look at the folder /etc/apache2/sites-available/ is the vhost file for this site there and is there maybe a copy of that vhost file with .err file extension?
Ok. Then double-check that you have set auto subdomain to 'www' in the website settings of that site. This must be set to www, otherwise the requests must show up on another website.
A few screenshots. The "interesting" thing is that the redirect from "www.mydomain.com" => "mydomain.com" in Edge, leads to a certificate error. This certificate goes to the first domain in the list of domains in ISPC3. I have tried to remove the certificate an re-create it from within ISPC3. Same results.
The way I see it, if the redirect works, then this wont' be a problem. Still weird though that the certificate doesn't cover the sub domain www
That's to be expected when the vhost is not responsible for the subdomain. As you can see in your screenshot, you did not set auto subdomain to www as it is required for the redirect you are doing, see post #9. Not weird at all, you configured it to not include www subdomain by setting auto subdomain to none.
Just as short explanation: The redirect handles that an incoming request that reaches the vhost gets rewritten. But by disabling the subdomain, these requests don't reach the vhost anymore.
