Want to subscribe to topics you're interested in?
Become a Member

missing cache enabler lines in conf in menu 22

Discussion in 'Bug Reports' started by dorobo, Sep 30, 2016.

  1. dorobo

    dorobo Active Member

    420
    104
    43
    Jun 6, 2014
    Ratings:
    +162
    Local Time:
    10:23 AM
    latest
    latest
    To reproduce:

    In centminmod main menu, choose 22

    enter domain
    ......
    ....
    ...
    Code (Text):
    Get Letsencrypt SSL certificate Nginx vhost? [y/n]: y
    
    You have 4 options: 
    1. issue staging test cert with HTTP + HTTPS
    2. issue staging test cert with HTTPS default
    3. issue live cert with HTTP + HTTPS
    4. issue live cert with HTTPS default
    Enter option number 1-4: 2
    


    and in
    Code (Text):
    --------------------------------------------------------
    (B[m[1;32;40m        Wordpress Caching              
    (B[m[1;33;40m--------------------------------------------------------
    (B[m[1;32;40m1). KeyCDN Cache Enabler (default & recommended)
    (B[m[1;32;40m2). Redis Nginx Level Caching (may have issues with some wp plugins)
    (B[m[1;32;40m3). Wordpress Super Cache
    (B[m[1;33;40m--------------------------------------------------------
    (B[mEnter option [ 1 - 3 ] 1
    


    but in


    domainname.com.ssl.conf

    it's missing the lines

    Code (Text):
    include /usr/local/nginx/conf/wpincludes/domainname.com/wpcacheenabler_domainname.com.conf;


    and

    Code (Text):
    try_files $cache_enabler_uri $uri $uri/ $custom_subdir/index.php?$args;


    which makes the internal links go 404
     
  2. dorobo

    dorobo Active Member

    420
    104
    43
    Jun 6, 2014
    Ratings:
    +162
    Local Time:
    10:23 AM
    latest
    latest
    ok I stand corrected. What will make the 2 lines disappear is when you finally decide to go live by issuing the command.

    Code (Text):
    ./acmetool.sh reissue domainname.com lived
     
  3. eva2000

    eva2000 Administrator Staff Member

    53,223
    12,116
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,654
    Local Time:
    12:23 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    yes that happens because acmetool.sh backs up existing domain.com.ssl.conf and recreates a new one so it knows where to sed replace the letsencrypt ssl certs using the acmetool.sh created self-signed ssl cert as placeholders in domain.com.ssl.conf

    really need to work on how to deal with re-running acmetool.sh on existing nginx ssl vhost based sites
     
  4. eva2000

    eva2000 Administrator Staff Member

    53,223
    12,116
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,654
    Local Time:
    12:23 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+