@butlerjw78: I had this problem on CentOS, too. It was SElinux blocking apache writing to the nonstandard location. Try “sudo setenforce 0” and see if the problem goes away; if it does, that’s the problem.
I solved it by setting the appropriate context:
chcon -R -t httpd_sys_rw_content_t <wp-dir>
