SSL Redirect on Login

[TheCableGuy96]

Hi guys,

So I have the following settings set:
port=2222
ssl_port=2223

If I login via ssl on 2223 it redirects me to port 2222 but it's still secure.

It's not so much a problem as it's still secure but would like to understand why it's redirecting me to a different port?

Any help is appreciated, thanks.

 

[factor]

maybe this

Version 1.59.0 | Directadmin Docs

DirectAdmin Knowledge Base

www.directadmin.com

ssl on port 2222

hi i enabled ssl on port 2222 but https is yellow and browser Warning: Potential Security Risk Ahead how to fix this ? and how to redirect http to https on port 2222 ? thank

forum.directadmin.com

 

[TheCableGuy96]

Thanks Brent, I don't think that's what's causing it. I re-set it up and re-wrote confs on 2 servers and now both servers are doing it so I think it's something new in DA which is forcing you to the non-ssl port.

I got round it by swapping the non-ssl port to 2223 and the ssl port to 2222. Now people stay on 2223 when logging in.

Cheers

 

[smtalk]

Is ssl=1 set there?

 

[TheCableGuy96]

Is ssl=1 set there?

Yes mate, on both servers

 

[Richard G]

Is ssl=1 set there?

That should not be needed according to the docs (click):

You do not need to set SSL=1 in your directadmin.conf. SSL=1 only affects the first port. The ssl_port will have ssl turned on by default.

 

[TheCableGuy96]

That should not be needed according to the docs (click):

Hi Richard,

Okay so I turned the default port back to 2222 and ssl port to 2223, changed to ssl=0, restarted DA and logged in via https://my.hostname.com:2223 which as soon as I logged in changed me to https://my.hostname.com:2222.... It has to be something in DA surely because it's happening on 2 servers now since I updated everything and re-wrote confs?

 

[Richard G]

Hello.
Well I can't imagine why this is happening. I only stated to smtalk that according to da's doc the ssl=1 was no requirement. But I already suspected that wouldn't make any difference for you.
Unfortunately I have no clue on to why it doesn't work and we only use port 2222.

 

[TheCableGuy96]

Hello.
Well I can't imagine why this is happening. I only stated to smtalk that according to da's doc the ssl=1 was no requirement. But I already suspected that wouldn't make any difference for you.
Unfortunately I have no clue on to why it doesn't work and we only use port 2222.

No worries, I appreciate the input pal. Could be a bug? Unfortunately I can't even talk to DA to discuss it as a possible bug because they now charge for support and it's only a personal server with an old lifetime license and can't really afford it.

 

[Richard G]

I don't know if it could be a bug. I don't have a test system otherwise I could check it for you.
Normally bugs could still be send via the ticket system and checked for free. If that isn't possible anymore then they must be reported on the forums.
Which you did. So lets hope that smtalk is checking this again and shine his light on this.
Maybe you might want to edit the thread title and add [bug] in front of it, to make clear this might be a bug.