Redirect Url for port 2222

T

thesilentman

Verified User
Joined
Jun 17, 2003
Messages
45
Hello there,

I just wanted to drop my feature request which shouldn't be too hard to include in DA.

Well, I'd like to run DA in SSL Mode but I only have a authenticated SSL for my own domain, so I'd like the customers to be redirected to controlpanel.myhostingcompany.com:2222 instead of getting that annoying certificate mismatch thingie when they log on 2222 on their domains.

Oh, yes I know one can include some html on his/her page and provide a login mechanism from outside directadmin, but I thought this request would be a nice addition, too.

Best regards,
Frank
 
You can easially do it with a vhost. There is no feature needed.

You also can redirect ssl connections with directadmin already via settings in the config file.
 
Hi SCSI,

What do you mean by easily with a vhost?

And which settings would that be in the directadmin.conf file?

I looked around in the forums but didn't find anything that would match what I want to do.

Let me just say again what I need.

Until now my clients login to ssl directadmin via port 2222 on their own domains.
Because they don't have valid ssl certificates for their domains they get warned by the browser.

I want to redirect their port 2222 to myssl.myhostingcompany.com:2222

So, Apache has no influence on port 2222 because directadmin is listening to it, ergo a redirect cannot be done there.

On the other side I could setup some subdomain (apache) without port 2222 on each customer domain that would the redirect to my directadmin port 2222.

But still I believe that the redirect should also be possible from within directadmin and redirect port 2222 (just in case a customer tries to login on their own 2222).

Best regards,
Frank
 
You cannot redirect ssl to ssl without a warning.

Use ssl_redirect_host=yourhost.com in /usr/local/directadmin/conf/directadmin.conf

You have to direct them over before they change to ssl or else you will always get an error.
 
I stopped giving my customers theirdomain.com:2222 in their welcome email and just game theservername.com:2222 instead. So everyone goes to the server's SSL/Cert on port 2222 and no errors. Seems to of cured alot of "why am i getting this error?" support tickets.
 
That's what I do. The problem occurs if you sell both retail and reseller hosting. In which case your resellers don't want their users to see your hostname.

The way we resolve that is to buy a generic domain name for our hosts.

Jeff
 
You must log in or register to reply here.
Back
Top