Posts by ShortSnow


    the /configs/debian/apache/parts/domain.tpl sets in case of #SECTION proxy_fwd BEGIN

    1. RequestHeader set X-Forwarded-Proto "http"RequestHeader set X-Forwarded-Port 80

    for both vhosts: SSL an not SSL. It would be perfekt if it sets for domain_ssl.conf

    1. RequestHeader set X-Forwarded-Proto "https"RequestHeader set X-Forwarded-Port 443

    Is it Possible to set different RequestHeaders via change in domain.tpl or a listener?

    My try to add row 4+5 and row 9/10 to ssl_proxy was not succesfull. The "#SECTION ssl_proxy BEGIN" as no effect.

    Thanks a lot



    kess: Yes you are right, but HSTS does not forward to SSL i think

    flames: Sorry i try to explain it better:

    If i enable a redirect for Domain with proxy, then two virtual hosts will be generatet. One for http and one for ssl. With a new Option for Redirekt (Example "Force SSL") The generated virtual host for Port 80 should have:

    1. RewriteEngine On
    2. RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L]

    instead of the Proxy Configuration.

    Thanks a lot



    i use very often the Proxy function for a Domain, which is very easy and perfect. I might be a little bit better, if there can be an option to force proxy over https.

    <> connected to IMSCP and set as Proxy to <> (where the content is located such as Wordpress)

    I can use and, both worked perfect. It will be a dream if there where an option to redirect http to https

    On the <> i have no chance to force to https, because always http.

    Thanks a lot for reading


    1. [email protected]:/home/admin# invoke-rc.d rsyslog rotate
    2. invoke-rc.d: action rotate is unknown, but proceeding anyway.
    3. [ ok ] Closing open files: rsyslogd.
    4. [email protected]:/home/admin# invoke-rc.d nginx rotate
    5. invoke-rc.d: action rotate is unknown, but proceeding anyway.
    6. [ ok ] Re-opening nginx log files: nginx.
    7. [email protected]:/home/admin#

    Hi Nuxwin,

    thanks for help and putting me in the right direction. I try to reproduce this with a backup of IMSCP 1.3.15 and update it again. Now the error is not there. So it is not usefull to spend more time in research of this problem.

    Thanks al lot and sorry for the time you spend on helping me.

    Greets ShortSnow

    Please close

    Hello Nuxwin,


    1. [email protected]:/home/admin# grep -nr invoke-rc.d /etc/logrotate.d
    2. /etc/logrotate.d/php5-fpm:10: invoke-rc.d php5-fpm restart > /dev/null
    3. /etc/logrotate.d/apache2:11: invoke-rc.d apache2 reload > /dev/null
    4. /etc/logrotate.d/rsyslog:10: invoke-rc.d rsyslog rotate > /dev/null
    5. /etc/logrotate.d/rsyslog:35: invoke-rc.d rsyslog rotate > /dev/null
    6. /etc/logrotate.d/nginx:16: invoke-rc.d nginx rotate >/dev/null 2>&1
    7. [email protected]:/home/admin#



    since Update ISCP 1.3.15 to 1.3.16 there is an empty file in /etc/logrotate.d -> imscp

    I think it is the reason for the Cron Mail:

    /etc/cron.daily/logrotate:invoke-rc.d: action rotate is unknown, but proceeding anyway.

    • i-MSCP 1.3.16

      • Build: 20170107

      • Codename: Horner
    • debian-jessie-amd64-hvm-2016-09-19-ebs on Amazon EC2
    • Plugins:

      • InstantSSH Version 5.0.1

      • LetsEncrypt Version 2.0.5

      • PanelRedirect Version 1.1.5

      • PhpSwitcher Version 2.3.2
    • Listeners

      • Nov 8 11:43

      • Dec 25 23:53

    Thanks a lot for your good Job.