View Single Post
Old 8th September 2012, 23:26
atjensen11 atjensen11 is offline
Senior Member
Join Date: Dec 2007
Posts: 199
Thanks: 9
Thanked 6 Times in 6 Posts

Thanks Falko.

I changed my configuration files slightly to make things a little easier (on me) to understand and configure.

I created a default vhost file for nginx as follows:
server {
    listen 80 default;
    server_name  _;
    access_log /var/log/nginx/default.access.log;
    error_log /var/log/nginx/default.error.log;

    location / {
        include /etc/nginx/proxy.conf;
I then created a symlink so that this vhost is loaded under /etc/nginx/sites-enabled.

My intent is to only define vhost files within nginx for the sites that have been moved to the new production server. The default vhost directives above should catch everything else and send the requests to the current (soon to be old) production server.

Does this sound like a logical approach to others?

With the nginx default vhost, I am now receiving a "No Input File Specified" error when browsing to the website. The website I am trying to browse to is running a PHP based content management system. I thought nginx would simply proxy through the dynamic content and let Apache serve up the dynamic content as it always has in the past.

I searched on this error and most who have encountered it have encountered it by running nginx as their webserver instead of a reverse proxy.

Any suggestions?
Reply With Quote