Wordpress Can't create user

maybe sure file permissions for migrated files and directories are correct see FAQ item 2 Getting Started Guide - CentminMod.com LEMP Nginx web stack for CentOS

 

normal for those main directories, under /public should be 755 for directories and 644 for files

Code (Text):

ls -lah /home/nginx/domains/newdomain.com/public
total 36K
drwxr-sr-x 2 nginx nginx  151 Aug 11 05:24 .
drwxr-sr-x 6 nginx nginx   56 Aug 11 05:24 ..
-rw-r--r-- 1 nginx nginx 1.6K Aug 11 05:24 403.html
-rw-r--r-- 1 nginx nginx 1.6K Aug 11 05:24 404.html
-rw-r--r-- 1 nginx nginx 2.1K Aug 11 05:24 500.html
-rw-r--r-- 1 nginx nginx 2.1K Aug 11 05:24 502.html
-rw-r--r-- 1 nginx nginx 2.2K Aug 11 05:24 503.html
-rw-r--r-- 1 nginx nginx 2.1K Aug 11 05:24 504.html
-rw-r--r-- 1 nginx nginx 2.2K Aug 11 05:24 50x.html
-rw-r--r-- 1 nginx nginx 1.2K Aug 11 05:24 index.html
-rw-r--r-- 1 nginx nginx 2.2K Aug 11 05:24 maintenance.html

 

Also to troubleshoot Nginx and PHP-FPM issues you'd want to check the domain site's vhost access.log and error.log logs located within directory at /home/nginx/domains/yourdomain.com/logs. You can see a full overview at centminmod.com/configfiles.html

FAQ item 19 has more info on all Centmin Mod relevant log files locations and how to use tail command to view a sample of the entries.

Also post the contents of your site's nginx vhost http /usr/local/nginx/conf/conf.d/yourdomain.com.conf and/or /usr/local/nginx/conf/conf.d/yourdomain.com.ssl.conf in BBCODE CODE tags as outlined at How to use forum BBCODE code tags | Centmin Mod Community

 

just replace actual domain name - references in vhost with domain.com via search and replace in text editor before posting

 

For you nginx vhosts for your domain.

For xenforo check out Nginx Rewrites for Xenforo Friendly Urls - CentminMod.com LEMP Nginx web stack for CentOS

For Wordpress & xenforo check out the vhost generator at Generate Centmin Mod Nginx Vhost - CentminMod.com LEMP Nginx web stack for CentOS to get an idea of what separately each web app's vhost should look like and you have some differences compared to what they should be.

You didn't mention if wordpress and xenforo are HTTPS default sites or not ?

FYI, notice you do not need a .php location context as include file in each nginx vhost takes care of that

Code (Text):

include /usr/local/nginx/conf/php.conf;

so your domain.com.ssl.conf vhost might be along the lines of below for starters

Code (Text):

# Centmin Mod Getting Started Guide
# must read http://centminmod.com/getstarted.html
# For HTTP/2 SSL Setup
# read http://centminmod.com/nginx_configure_https_ssl_spdy.html

# redirect from www to non-www  forced SSL
# uncomment, save file and restart Nginx to enable
# if unsure use return 302 before using return 301
# server {
#   server_name domain.com www.domain.com;
#   return 302 https://$server_name$request_uri;
# }

server {
  listen 443 ssl http2;
  server_name domain.com www.domain.com;

  ssl_dhparam /usr/local/nginx/conf/ssl/domain.com/dhparam.pem;
  ssl_certificate      /usr/local/nginx/conf/ssl/domain.com/domain_com.crt;
  ssl_certificate_key  /usr/local/nginx/conf/ssl/domain.com/domain.key;
  include /usr/local/nginx/conf/ssl_include.conf;

  http2_max_field_size 16k;
  http2_max_header_size 32k;
  # mozilla recommended
  ssl_ciphers EECDH+CHACHA20:EECDH+CHACHA20-draft:EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA256:EECDH+ECDSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+SHA384:EECDH+AES128:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA:!CAMELLIA;
  ssl_prefer_server_ciphers   on;
  #add_header Alternate-Protocol  443:npn-spdy/3;

  # before enabling HSTS line below read centminmod.com/nginx_domain_dns_setup.html#hsts
  #add_header Strict-Transport-Security "max-age=31536000; includeSubdomains;";
  #add_header X-Frame-Options SAMEORIGIN;
  #add_header X-Xss-Protection "1; mode=block" always;
  #add_header X-Content-Type-Options "nosniff" always;
  #spdy_headers_comp 5;
  ssl_buffer_size 1369;
  ssl_session_tickets on;

  # enable ocsp stapling
  resolver 8.8.8.8 8.8.4.4 valid=10m;
  resolver_timeout 10s;
  ssl_stapling on;
  ssl_stapling_verify on;
  ssl_trusted_certificate /usr/local/nginx/conf/ssl/domain.com/ssl-trusted.crt;

# ngx_pagespeed & ngx_pagespeed handler
#include /usr/local/nginx/conf/pagespeed.conf;
#include /usr/local/nginx/conf/pagespeedhandler.conf;
#include /usr/local/nginx/conf/pagespeedstatslog.conf;

  # limit_conn limit_per_ip 16;
  # ssi  on;

  access_log /home/nginx/domains/domain.com/log/access.log combined buffer=256k flush=5m;
  error_log /home/nginx/domains/domain.com/log/error.log;

  include /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf;
  root /home/nginx/domains/domain.com/public;
  # uncomment cloudflare.conf include if using cloudflare for
  # server and/or vhost site
  #include /usr/local/nginx/conf/cloudflare.conf;
  include /usr/local/nginx/conf/503include-main.conf;

  location / {
    include /usr/local/nginx/conf/503include-only.conf;
    rewrite ^/(threads|forums|members|blog)/(.*)$ /forum/$1/$2 redirect;
  
    # Wordpress Permalinks
    try_files $uri $uri/ /index.php?q=$request_uri;

    include /usr/local/nginx/conf/wpsecure.conf;
    include /usr/local/nginx/conf/wpnocache.conf;
  }

  location /forum/ {
    index index.php index.html;
    try_files $uri $uri/ /forum/index.php?$uri&$args;
 
  }
  location /forum/install/ {
      include /usr/local/nginx/conf/php.conf;
      internal;
  }
  location /forum/internal_data/ {
      internal;
  }
  location /forum/library/ {
      internal;
  }

  include /usr/local/nginx/conf/staticfiles.conf;
  include /usr/local/nginx/conf/php.conf;
  include /usr/local/nginx/conf/drop.conf;
  #include /usr/local/nginx/conf/errorpage.conf;
  include /usr/local/nginx/conf/vts_server.conf;
}

 

then focus on getting domain.com.ssl.conf working first

 

yes extra deny/allow isn't needed for internal directives start with my suggested vhost first

 

Was your original wordpress install http or https based ? If it was http based and you now enable https on centminmod, the wordpress based install is still http not https.

If all else is working now just user edit/add blank, then something else is causing it

Try disabling all WP plugins + restart nginx and php-fpm to clear caching and try adding user to see if that works. Troubleshoot WP plugins first.

Also the logs mentioned at Wordpress - Can't create user as sometimes you could be caught in tools/autoprotect.sh cronjob feature outlined at Beta Branch - autoprotect.sh - apache .htaccess check & migration to nginx deny all | Centmin Mod Community. You can quickly confirm if it's the case by commenting out the include line

Code (Text):

include /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf;

You uploaded scripts may have .htaccess deny from all type files in their directories which may need bypassing autoprotect. It's a security feature that no other nginx based stack has as far as I know

So instead, all .htaccess 'deny from all' detected directories now get auto generated Nginx equivalent location match and deny all setups except if you want to manually bypass the directory from auto protection via a .autoprotect-bypass file - details below here.

You can read a few threads below on how autoprotect.sh may have caught some folks web apps falsely and the workarounds or improvements made to autoprotect.sh with the help of users feedback and troubleshooting.

• Is it better to add an exeption for 127.0.0.1 for autoprotect rules? | Centmin Mod Community
• IP.Board - Query on autoprotect + IPB forums | Centmin Mod Community
• Wordpress - Akismet JS and CSS - Forbidden? | Centmin Mod Community
• Nginx - Error 403 nginx with sngine script

 

if it's #3, don't delete .htaccess files as they come back when you update your scripts/upload new sets of files so instead setup bypass files in those directories Beta Branch - autoprotect.sh - apache .htaccess check & migration to nginx deny all or just comment out with hash # in front of the line

Code (Text):

#include /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf;

then restart nginx+php-fpm

Code (Text):

nprestart

 

yeah if you comment out /usr/local/nginx/conf/autoprotect/domain.com/autoprotect-domain.com.conf it is enough to disable the autoprotect feature.

might need to ask on wordpress support forums for clues

• Forum: Fixing WordPress « WordPress.org Forums
• WordPress Development Stack Exchange

 

problem is with the wordpress database itself it seems do you still have original wordpress backup .sql file you created from old server ? do you have access to old server still ? if you have access to old server, might want to make a new sql backup and try that

https://spigotdesign.com/wordpress-log-redirect-loop/