DirectAdmin on SSL

kristian

kristian

Verified User
Joined
Nov 4, 2005
Messages
468
Location
Norway
Hi,

I've successfully created a self-signed certificate for testing, and put DA on SSL.

However, now the non-ssl URL is unaccessible. Is there a way for DA to redirect requests for http://host:2222/ to https://host:2222/?

Any other method I can use to make the transition smoother than sending an email to all customers on the server telling them of the change?
 
kristian said:
Hi,

I've successfully created a self-signed certificate for testing, and put DA on SSL.

However, now the non-ssl URL is unaccessible. Is there a way for DA to redirect requests for http://host:2222/ to https://host:2222/?

Any other method I can use to make the transition smoother than sending an email to all customers on the server telling them of the change?
Click to expand...

Any news on this? I am having the same issue and it's a huge support issue for us, we have to keep telling customers to manually add the "S" in the https://.

I will send an email to DA support to see if they can chime in here and help us.
 
jlasman said:
Works for me.
http://da6.namelessnet.net:2222/ redirects automatically to https://67.30.130.180:2222/.

And http://67.30.130.180:2222/ does the same.

Jeff
Click to expand...

Very strange, seems to work for me too off and on...

Can't explain why it re-directs sometimes and others it doesn't.

Ahh Huh!

Just noticed this..

Let's say I have a customer who has a domain of "somedomain.com"

If he goes to http://www.somedomain.com:2222 it redirects to SSL just fine, if however he goes to http://somedomain.com:2222 it barfs.

I tried to get the error and copy/paste it from FireFox but now it just gives me a blank white page. I think it was giving me an error before but I can't say for sure.

Yes the site does come up fine just going to somedomain.com just not when going to somedomain.com:2222.
 
Hello,

The *only* purpose of the redirect is to remind people that they forgot to use the https. The mere fact that DA can even *do* the redirect is impressive because it's talking http through an https encrypted socket. I'm not aware of any other program that can do that.

The IP that gets returned for the rediect is that of the server IP.
Since the browser tried talking http to an https connection, the headers are all chewed up and lost in the ssl routines that are trying to say "hi" in the handshake. That of course fails... at which point DA figures... all is lost, so might as well try sending the redirect to the user.

www.domain.com:2222 vs just domain.com:2222 will make no difference. The host value isn't looked at for this. All that matters is if you connect to any IP in DA via http on an https connection, you'll get redirected to the server IP on https, as that's DA's only option to give the user, it doesn't know anything else at that point (requested headers are lost)

John
 
DirectAdmin Support said:
Hello,

The *only* purpose of the redirect is to remind people that they forgot to use the https. The mere fact that DA can even *do* the redirect is impressive because it's talking http through an https encrypted socket. I'm not aware of any other program that can do that.

The IP that gets returned for the rediect is that of the server IP.
Since the browser tried talking http to an https connection, the headers are all chewed up and lost in the ssl routines that are trying to say "hi" in the handshake. That of course fails... at which point DA figures... all is lost, so might as well try sending the redirect to the user.

www.domain.com:2222 vs just domain.com:2222 will make no difference. The host value isn't looked at for this. All that matters is if you connect to any IP in DA via http on an https connection, you'll get redirected to the server IP on https, as that's DA's only option to give the user, it doesn't know anything else at that point (requested headers are lost)

John
Click to expand...

I get what you are saying but it just seems that it's not consistant, I got a ticket from a customer saying he couldn't get the control panel, he gave me the link, I clicked it and I could get there either. Seems later it just worked..

Beats me, I guess I don't have enough info other than it seems to work sometimes and not others. Again, not much info, I just know it's not working every time, otherwise I wouldn't have made this post. :)
 
Hi,

We changed over all our servers to use https logins around a month ago, and ever since then we've had various customers saying they cant get to the login but we've told them to try again and it works fine !
We've assumed this was the odd customer not pressing "go" or their connection to the server not being great. However its also happening to us, and some of the resellers on the servers have also now reported the problem.

Is anyone else here still having the problems ? can they confirm what browser(s) they are having the problems in, and what the server is ?

We are getting it in both IE7 and Firefox, but not in IE6 ! Running CentOS on the servers, with latest version of DA.

Also - anyone who thinks they are not having the problem, can you post the url to the http that then redirects to see if we get the problem on your boxes?

Would like to get this solved now I know its not just customers being stupid.

Thanks.

Tom
 
I had this problem aswell.. in the end i just kept the normal port as http and opened an new one on https, then emailed the cosuters the new https url and hoped they used it.
 
You must log in or register to reply here.
Back
Top