New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Is it re-directing to the server address / IP?
Did you just add the cert to your domain/site under the client panel or activate it under WHM > Manage Service SSL Certificates ?
Hi wych. I have added it via cpanel and it shows on WHM certs and it is working for the domain.
When I type https://mydomain.com/cpanel it redirects to https://mydomain.com:2087 and it says your connection is not private.
It's very much usual. You've to install certs in Manage Service SSL to get rid of this problem.
Ok intalled it via whm still the same problem.
I don't think you are following the flow of the conversation,
Home »Server Configuration »Tweak Settings
SSL redirect destination should be hostname, thenHome »Service Configuration »Manage Service SSL Certificates
Install your cert as long as it is valid for the hostname.Is your cert for a site or the server hostname?
Only for the site not server hostname.
And where does cPanel redirect you to ?
You wont be able to use your cert (non hostname) for cpsrvd . This feature is still not included in cPanel.
You will need a cert for the hostname if you want clients to not get the warning then and set the redirection as I directed
Set redirection for ssl to ssl name
@WHT Do you have ROOT Access ??
I don't know much about apache/cpanel/whmcs and all that, but is the webserver listening on your ssl port?
Yes
Install on hostname, go to tweak setting -> set redirect to host. browse via hostname:2087/2083
You can't get the SSL working on anydomain.com:2087. cPanel has not implemented system for this. So, force your customers to use hostname:2087
There must be a way. How did miTgiB on his website (check his signature). He is using his domain not hostname.
You want for the users cPanel and WHM on ports 2083/2087 correct? To get that you need to have a cert that matches on the service ports, so you redirect to the hostname and have a cert that matches the hostname. This has been explained by many in this thread, so I have to assume you are not understanding a part of what is being explained. But I have a wildcard so *.hostigation.com is valid, and any client on shared hosting can goto https:their.doma.com/cpanel and they will be redirected to the hostname of the server, so https://anything.hostigation.com:2083 will be where they go, and my wildcard will be valid.
Is there any part of this you are still not understanding? And you do not need to get a wildcard, I just have use for more certs on hostigation.com that a wildcard is cheaper than $5 per subdomain for a cert.
@miTgiB
If am your client and I install a certificate on mydomain.com can I access cpanel with https://mydomain.com:2083 without to redirect me on your hostname?
You can, but your cert will not match, since it is not valid for the hostname, most likely. This is why you redirect to the hostname, so the client visits https://mydomain.com/cpanel and gets redirected to https://host.name.com:2083 and you install a valid cert for the host. Now they get a valid cert that matches and no browser warning from the SSL conspiracy nuts
Ok so it means I can not access cpanel secure connection via my domain without to be redirected to servers hostname?
Correct, visit http://bigtim.net/cpanel to see this in action and here is how I have it set in tweak settings http://imgur.com/WAI8W1j
Intresting. Thank you everyone! Am still not giving up. Just opened a ticket with cpanel.
Why? You cannot have multiple certs for the service ports, think a little