No, that didn't work at all. Everything was returning a "no input file specified" error. One thing I forgot about until just now are two included files in this config.
The part:
Code:
##what do we do with php files
location ~ \.php$ {
include fastcgi_params;
include fastcgi_config;
}
loads up the two following files:
fastcgi_params
Code:
fastcgi_param QUERY_STRING $query_string;
fastcgi_param REQUEST_METHOD $request_method;
fastcgi_param CONTENT_TYPE $content_type;
fastcgi_param CONTENT_LENGTH $content_length;
fastcgi_param SCRIPT_NAME $fastcgi_script_name;
fastcgi_param REQUEST_URI $request_uri;
fastcgi_param DOCUMENT_URI $document_uri;
fastcgi_param DOCUMENT_ROOT $document_root;
fastcgi_param SERVER_PROTOCOL $server_protocol;
fastcgi_param GATEWAY_INTERFACE CGI/1.1;
fastcgi_param SERVER_SOFTWARE nginx/$nginx_version;
fastcgi_param REMOTE_ADDR $remote_addr;
fastcgi_param REMOTE_PORT $remote_port;
fastcgi_param SERVER_ADDR $server_addr;
fastcgi_param SERVER_PORT $server_port;
fastcgi_param SERVER_NAME $server_name;
# PHP only, required if PHP was built with --enable-force-cgi-redirect
fastcgi_param REDIRECT_STATUS 200;
fastcgi_config
Code:
fastcgi_split_path_info ^(.+\.php)(.*)$;
fastcgi_pass backend;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME /home/mydomain/www$fastcgi_script_name;
# fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param QUERY_STRING $query_string;
fastcgi_param REQUEST_METHOD $request_method;
fastcgi_param CONTENT_TYPE $content_type;
fastcgi_param CONTENT_LENGTH $content_length;
fastcgi_intercept_errors on;
fastcgi_ignore_client_abort off;
fastcgi_connect_timeout 60;
fastcgi_send_timeout 180;
fastcgi_read_timeout 180;
fastcgi_buffer_size 128k;
fastcgi_buffers 4 256k;
fastcgi_busy_buffers_size 256k;
fastcgi_temp_file_write_size 256k;
Something that stands out is the
Code:
fastcgi_param SCRIPT_FILENAME /home/mydomain/www$fastcgi_script_name;
and I am wondering if this is what is giving me problems. I've tried switching it with the commented line below it but I just get blank pages with no errors. That might actually be the key issue, yet I'm not knowledgeable enough with nginx to understand how to re-configure it.
So as of the moment, I can do the following:
- Access the "front" portion of the site, which is drupal and all it's SEO-friendly urls like mydomain.net/videos, mydomain.net/great-news-article, and mydomain.net/gallery/picture2
- Access a vbulletin install in a subdirectory, /forums
- Access the landing page for the XenForo install, clicking on any link that uses the forum software takes me to a blank drupal page. Unchecking "Use Full Friendly URLs" in Xenforo lets me use the software without issue.