Imtek
Verified User
On all of our machines the webapps running (for instance domain.com should be redirected to https:/webX.hostname.tld/roundcube on the hostnames are not forced to SSL anymore an remains unsecure on http:/webX.hostname.tld/roundcube.
Has something changed in the logic of DirectAdmin?
In options.conf we have:
redirect_host=webX.hostname.tld
redirect_host_https=yes
use_hostname_for_alias=yes
In directadmin.conf we have:
force_hostname=webX.hostname.tld
ssl_redirect_host=webX.hostname.tld
Also checked if there where some custom configs causing this issue. But also checked and found that is not the issue.
Also in /etc/httpd/conf/extra/httpd-alias.conf i see the https links are correctly specified.
We use nginx_apache by the way, any thougths?
Has something changed in the logic of DirectAdmin?
In options.conf we have:
redirect_host=webX.hostname.tld
redirect_host_https=yes
use_hostname_for_alias=yes
In directadmin.conf we have:
force_hostname=webX.hostname.tld
ssl_redirect_host=webX.hostname.tld
Also checked if there where some custom configs causing this issue. But also checked and found that is not the issue.
Also in /etc/httpd/conf/extra/httpd-alias.conf i see the https links are correctly specified.
We use nginx_apache by the way, any thougths?
Last edited: