How to redirect domain https://A to domain https://B

Digital Essence

Digital Essence

Verified User
Joined
Jan 9, 2023
Messages
21
Hi,

I've searched the forums but so far not found any threads or docs that help. I know this is more a failure of my search skills or understanding of the responses so please bear with me.

I have a customer with two domains and I want to redirect domain A to B. I've logged in as that user in DA and added a Site Redirection on domain A to B. This works fine if I use a http version of domain A but gives me a NET::ERR_CERT_COMMON_NAME_INVALID error if I use the https version.

I require two domains rather than a pointer as we also need to forward emails from domain A to domain B.

Looking forward to your advice. Thank you.
 
Digital Essence said:
This works fine if I use a http version of domain A but gives me a NET::ERR_CERT_COMMON_NAME_INVALID error if I use the https version.
Click to expand...
I have the same, but using the old skin, one can only use the "domain.com" without http or https in front of it, and this works fine.

In my skin (enhanced skin) it looks like this.
/301https://www.domainB.com/

DA then creates a .htaccess redirect with the same content:
Redirect 301 / https://www.domainB/

But it doesn't matter if a customer visits http://domainA.com or https://domainA.com, in both cases they are redirected to https://domainB.com.
Doesn't the browser work the same in your case, not even another browser or when refreshing?

Digital Essence said:
I require two domains rather than a pointer as we also need to forward emails from domain A to domain B.
Click to expand...
You are aware of the fact that if you have for example an existing [email protected] any mail to [email protected] will be send to [email protected] in case of a pointer?
And then can be answered from [email protected] (and not from [email protected] anymore)?
So you could use points as far as I can see.
 
open4biz said:
Also, are you trying to go https to http at all? Apparently that's disallowed
Click to expand...
You're wrong. That doesn't matter at all as you can see from my screenshot it is allowed. Might be a skin issue maybe.
I have hobby domains running on DA which work the way as described, with https, without any issue.

Having nameservers externally is possible, but also has his downsides. It's a choice. I personally would never go back to external servers. But that's everyone's free choice ofcourse.
 
Hi Richard,

finally got time to look into this.

The redirection doesn't work in a browser I never normally use (Edge).

If I visit http://DomainA it redirects to https://DomainB

If I visit https://DomainA I get a cert warning, if I click Advanced/Proceed I get a page that says "is functioning normally"

I've tried changing skins and recreating the site redirect which by the way doesn't show http or https in the local URL path, just the domain name but no difference in behaviour.

In terms of pointers. Are you saying that if I have a main domain (one in bold) that if I add a pointer to it then all info@ pointer will go to info@ main domain?

Thanks,
 
Hello.

Digital Essence said:
If I visit https://DomainA I get a cert warning, if I click Advanced/Proceed I get a page that says "is functioning normally"
Click to expand...
I'm sorry you are correct. I just visit domain.com and get redirected to https://otherdomain.com but I never use https:// manually in front of it, so that is the reason I haven't seen this. However I don't know if or how this can be solved either. I got a ssl notice no the apache notice.
Sorry to have been incomplete with the information.

Digital Essence said:
In terms of pointers. Are you saying that if I have a main domain (one in bold) that if I add a pointer to it then all info@ pointer will go to info@ main domain?
Click to expand...
Yes that is correct. But it's like this.
It's send to [email protected] but in the to field you still will see [email protected] so you know that it's coming from the pointer. That makes it easier to correct people sending to the pointer domain.
Also, if you click reply on that mail, the "from" mail address will by [email protected] so [email protected] will not be used.
 
Hi Richard,

Code: 
If I visit https://DomainA I get a cert warning, if I click Advanced/Proceed I get a page that says "is functioning normally"If I visit https://DomainA I get a cert warning, if I click Advanced/Proceed I get a page that says "is functioning normally"


Does DomainA has a SSL Certificates ?
if not go to DomainA DA panel and creat a free SSL Certificates
 
Hi,

you can add cname record for ssl Validation
Domain Control Validation (DCV) Methods

but i don't know let's Encryptet offer this and working whit DA and let's Encrypt
what i know ther is (DCV) Methods. But i am not expert on.


you can remove Redirect 301 / https://www.domainB/
and creat a free ssl for the domainA and recreat the Redirect 301 / https://www.domainB/ again
so you have (~3 months) time to find other mehtods until ssl end.

Regards.
 
Thank you, however this is for a hobby domain of myself, most people just visit it via domain.com and are then redirected automatically to the https main domain so they won't enounter the ssl page. I don't really have an issue with that. Mainly also because the pointer domains are almost never visited anymore. Everyone uses the main domain.

It was @Digital Essence looking for some solution and I posted mine as a possible option. He might need to use a domein with redirect instead of a pointer for this purpose. For email a pointer would be enough.
 
another way, Just create normal domain. And use "Custom HTTPD Configurations" from Admin Role
and set DOCROOT to domain_b ( this work like Domain Pointer ). But you can create SSL, you can forward email from domain_a to domain_b


for APACHE or NGINX, just use "CUSTOM" token variable

if you use nginx_apache reverse proxy, you need to set both Apache and Nginx
Code: 
|?DOCROOT=`HOME`/domains/domain_b.com/public_html|
 
You must log in or register to reply here.
Back
Top