Forward to new domain without ssl warning with site redirection feature

[Magistar]

Hi I need to forward olddomain.com to newdomain.com. Normally I would use site direction for this.

Problem: Currently let's encrypt is used and in 34 days it will expire. So after that due to the forwarder I assume it cannot renew. I tried to disable ssl entirely in directadmin settings hoping the https wil automatically forward to http. But if you visit the https://olddomain.com there wil be a browser warning. It will not forward and the page will read apache is running.

How do I properly keep the olddomain forwarded through the new domain?

 

[kristian]

I'm not 100% sure, but I believe the .well-known alias used for the web challenge will kick in before the redirect, so having a normal LE cert should still work. Alternatively you can make it a wildcard cert, which will use DNS challenge instead, meaning any http redirects will not affect the challenge process.

 

[Richard G]

I was following this as I had a kindlike issue on a vps of a customer.
Domain A was redirected to Domain B on another VPS. But it seemd the SSL was checked before the redirect. And since domain B was not on the current VPS, an SSL error would appear logically.
So exactly the same issue. And this is not solved with a wildcard certificate as domain B is not present on server A anymore.

In fact to be able to prevent this, the redirect should take place before the SSL check. I tried both redirect from DA as with a .htaccess file but that didn't matter.

Which is why I liked this question because I was wondering about this too. Because imho this should not happen.
But since domain B is visited first to be able to see the redirect, it might also be normal. I don't know.

 

[johannes]

Happened to me also. Cannot make https redirect to other domain without ssl error, only http redirect. Seems systemical prob.