Alias domains and HTTPS

4u123

Well-Known Member
PartnerNOC
Jan 2, 2006
866
15
168
We are receiving increasing reports from customers about certificate mismatch issues when dealing with aliases and redirects.

As the world goes https, unfortunately cpanel aliases are getting left behind. A customer can no longer easily redirect one domain to another without getting SSL errors.

Obviously, Aliases don't have a vhost entry and they can't have their own certificates - so adding them at all now seems almost completely pointless, when the entry point to most domains in whatever form is almost always https now.

It's impractical to ask a customer to purchase more addon domains just so they can redirect one domain to another.

The issue often stems from Google results - where it seems all URL's contain https - even if the domain is not https enabled.

Its really hard to tell a customer that there's nothing we can do to help with this issue.

There is clearly a need for customers to redirect domains to other domains and this is most definitely the job of the web server. I do hope cpanel have a solution going forward. Perhaps there is a way to have a vhost entry and autossl certificate, without allowing for a website to be hosted from the domain?

Something needs to be done though.
 

cPanelMichael

Technical Support Community Manager
Staff member
Apr 11, 2011
47,749
2,205
363
cPanel Access Level
DataCenter Provider
Twitter
Hello @4u123,

Using Addon domains (which have their own virtual hosts) instead of Aliases is the best "workaround" for the issue you have described. However, your concern is understandable, especially since you noted a desire to avoid the need to increase the number of addon domains allowed per account.

I recommend sharing this feedback as a feature request via our feature request website. Here's the format we recommend using when creating a feature request to ensure your feedback gets as much visibility as possible and translates into actionable work:

As a {cPanel User, System Administrator, web-hosting provider, or any other user perspective}, I would like {the feature that is being requested} so that {benefit that the request adds to the product}.
Feel free to respond here with a link to the feature request upon approval and I can begin sharing the link to spread awareness.

Thank you.
 

4u123

Well-Known Member
PartnerNOC
Jan 2, 2006
866
15
168
A feature request is not appropriate here, simply because this issue affects the basic functionality of your platform. It's something you should have discussed internally and already found a solution for - and already implemented!

The fact is that parked domains (aliases) have become completely defunct because they don't work with https - and this affects our customers right now. Why haven't you anticipated this issue and done something about it?

It's cpanels job to find a solution that allows the end user to redirect domains, retaining the functionality of aliases and ensuring that visitors won't receive errors in the browser. You need to keep up with the development of your product and find solutions before these issues arise.

I'm sure there are a number of ways you can achieve this - but it is certainly not the responsibility of your customers to suggest ways in which you do that. I don't work for you.