Enabling "redirect to https" does not generate nginx config with redirect

Discussion in 'ISPConfig 3 Priority Support' started by Haringstad, Nov 12, 2022.

Tags:
  1. Haringstad

    Haringstad New Member HowtoForge Supporter

    Hello all,
    I am facing a weird problem. I do have a couple of servers in a multi-server setup.
    One of these servers does not generate the redirect to https parts anymore in the nginx configs. While the other 4 servers still do.
    On all servers, there are the same versions of NGINX, PHP, and ISPConfig.
    While in the DB, the field rewrite_to_https: y , no redirect part is written in the vhost config.
    With debug enabled, I do also not see any errors.
    Please advise, what you need to help me out, debugging this issue?
    High regards,
    Jacco
     
    Haringstad, Nov 12, 2022
    #1
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Enable debug mode and comment out server.sh cronjob, then disable SSL redirect, press save, enable SSL redirect again, run server.sh as root on the shell and post the output that you get on the shell.

    Beside that, have a look at the directory /etc/nginx/sites-available/ if there is a chost file for this website that ends with .err file ending.
     
    till, Nov 12, 2022
    #2
    Haringstad likes this.
  3. Haringstad

    Haringstad New Member HowtoForge Supporter

    Till, Thank you for your swift reply.
    - There are no vhosts with an .err in the /etc/nginx/sites-available directory. So that is a good thing.
    ls: cannot access '/etc/nginx/sites-available/*.err': No such file or directory
    Output of running server.sh:
     

    Attached Files:

    Haringstad, Nov 12, 2022
    #3
  4. Haringstad

    Haringstad New Member HowtoForge Supporter

    And here the vhost file:
     

    Attached Files:

    Haringstad, Nov 12, 2022
    #4
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    The https redirect is there, see:

    Code:
    if ($scheme != "https") {
            rewrite ^(?!/\.well-known/acme-challenge)/ https://$http_host$request_uri? permanent;
        }
    So the Nginx redirect is correctly created and present in the vhost. Most likely the behavior you see is either caused by the many additional Nginx rules you inserted or by WordPress itself.
     
    till, Nov 13, 2022
    #5
  6. Haringstad

    Haringstad New Member HowtoForge Supporter

    Till, thank you.
    I was under the assumption that there was a section, like in the older versions, that was listening to port 80, and from there redirecting.
    This is probably changed. (I'm going to check changelogs). I am thankful for your "eyes" on this issue, and we will check the additional nginx rules, to see if those may pose the issue. (which I hope not). Thank you again, and keep up the superb work!

    Jacco
     
    Haringstad, Nov 13, 2022
    #6

Share This Page