Support

Admin Tools

#27332 Redirect old to new domain with https : error

Posted in ‘Admin Tools for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Admin Tools version
n/a

Latest post by on Thursday, 13 April 2017 17:17 CDT

Monday, 13 March 2017 18:05 CDT

BigStef
 Hi...
I have made recently a migration of a website from an old domain to a new one.
Tha's the way I did it in this order :

1/ Create an account with new domain (new-dom.com)
2/ Migrate website with Akeeba Backup
3/ Close old account with old domain (old-dom.com)
4/ Create in new-dom.com account, a parked domain for old-dom.com
5/ In AT htaccess Maker , param "Redirect this (old) domain name to the new one" with 'old-dom.com'
6/ In AT htaccess Maker , param "HSTS Header (for HTTPS-only sites)" on 'Yes'

And most of redirect works. Except one thing I don't know how to solve :
Old https://www.old-dom.com URL make an security error ...
If I simply enter http://www.old-dom.com, the URL is correctly redirected...
Any suggestion ?

Stephan Herby PAO Production New Caledonia - Canada - France

Edited by BigStef on 2017-03-13 18:06 CDT

Tuesday, 14 March 2017 01:01 CDT

nicholas
If you wanted to do that you would need the new server to be able to serve both domains AND have two SSL certificates installed for both the old and the new domain.

What you've done now is that the new server to is able to serve both domains BUT ONLY have one SSL certificates installed, for the new domain. Therefore when a client tries to connect to your old domain one of two things happens:

a. if they had visited the domain before. The HSTS header had told the browser to remember that this site is server through HTTPS and that this is the certificate to expect. The browser receives a different certificate on HTTPS handshake and throws an error.

b. if they had never visited the domain before. The HTTPS handshake serves a certificate for the new domain which is NOT the domain the browser tried to connect to. Therefore it throws an error about a valid certificate in the wrong domain being used.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 14 March 2017 09:23 CDT

BigStef
Hi Nicholas,
Your clears explanations gave me an idea. I just add a Let's Encrypt certificate for the old domain old-dom.com on my Cpanel and it seems every things works now.
Thank you very much for your help here that does not really relate with AT :)

Stephan Herby PAO Production New Caledonia - Canada - France

Tuesday, 14 March 2017 10:00 CDT

nicholas
You're welcome! I'm glad I could help after all :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 13 April 2017 17:17 CDT

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
Edited by on 2017-04-13 17:17 CDT

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!