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

Wordpress Error on new Wordpress install

Discussion in 'Blogs & CMS usage' started by mayorjc, Aug 12, 2020.

  1. mayorjc

    mayorjc New Member

    10
    1
    3
    Jun 18, 2018
    Ratings:
    +4
    Local Time:
    6:58 AM
    Hi y'all

    I attempted to add another Wordpress site to my server via option 22 with cloudflare in front (newdomain.com). The fresh install had a 403 error immediately. I have 4 other sites with this configuration and no issues. Autoprotect was not the issue.

    After deleting the vhost via the WP uninstaller script, visiting newdomain.com in browser would produce all the content of a different site (othersite.com) on my server without any re-routing (eg the browser still shows newdomain.com).

    Appreciate any insights on what might be driving this and how I can further go about debugging.

    Thanks!
     
  2. mayorjc

    mayorjc New Member

    10
    1
    3
    Jun 18, 2018
    Ratings:
    +4
    Local Time:
    6:58 AM
    Some information about the server:
    • CentOS Version: CentOS 7 64bit
    • Centmin Mod Version Installed: 123.09beta01
    • Nginx Version Installed: 1.19.0
    • PHP Version Installed: 7.4.7
    • MariaDB MySQL Version Installed: 10.3.24
    • When was last time updated Centmin Mod code base ? : 8/10/2020
    • Persistent Config:
    Code:
    MARCH_TARGETNATIVE='y'
    LETSENCRYPT_DETECT='y'
    DUALCERTS='y'
    NGINX_SSLCACHE_ALLOWOVERRIDE='y'
    SET_DEFAULT_MYSQLCHARSET='utf8mb4'
    AUTOHARDTUNE_NGINXBACKLOG='y'
    ZSTD_LOGROTATE_NGINX='y'
    ZSTD_LOGROTATE_PHPFPM='y'
    
    
    NGINX_LIBBROTLI='y'
    NGXDYNAMIC_BROTLI='y'
    PHP_PGO_ALWAYS='y'
    PHP_PGO='y'
    PHP_BROTLI='y'
    PHP_LZFOUR='y'
    PHP_LZF='y'
    PHP_ZSTD='y'
    PHPFINFO='y'
    AUDITD_ENABLE='y'
    
     
    Last edited: Aug 12, 2020
  3. mayorjc

    mayorjc New Member

    10
    1
    3
    Jun 18, 2018
    Ratings:
    +4
    Local Time:
    6:58 AM
    I'm still curious to understand how this may have happened.

    Yet I'm happy to report that I did a (fourth) uninstall and reinstall, excluding Letsencrypt / including self-signed SSL while Cloudeflare paused. Site created successfully without these other troubles.

    Thanks again for the brilliance that is CMM!
     
  4. eva2000

    eva2000 Administrator Staff Member

    45,201
    10,280
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +15,934
    Local Time:
    9:58 PM
    Nginx 1.19.x
    MariaDB 5.5/10.x
    Great to hear

    That is normal if nginx vhost's server_name exists it tells nginx to route domains listed in vhost's server_name to the right domain/site. But if you delete the nginx vhost and still have DNS record for deleted domain pointing to server IP, then it will usually route to the server's main hostname nginx vhost at /usr/local/nginx/conf/conf.d/virtual.conf which is Getting Started guide step 1 setup Getting Started Guide - CentminMod.com LEMP Nginx web stack for CentOS and Centmin Mod Configuration Files - CentminMod.com LEMP Nginx web stack for CentOS as virtual.conf nginx vhost has listen directive with default_server flag which is like a catch all. If you re-add the missing nginx vhost and server_name, then nginx will route correctly as you found out