Quantcast
Channel: Nginx Forum - How to...
Viewing all articles
Browse latest Browse all 4759

Re: accessing two different sites by 192.x.x.x/test1 and 192.x.x.x/test2 possible?

$
0
0
Thanks for your reply.

I knew that I was not totally wrong. To give some more details about my configuration:

I defined two sites in the "sites-available" folder of nginx.

Here is the one for owncloud:

server {
listen 8080;

root /var/www;
access_log /var/log/nginx/access_log_custom1;

server_name cloud;


location /cloud {
root /var/www/cloud;
index index.html index.php;
}



location ~ \.php$ {
fastcgi_intercept_errors on;
fastcgi_pass unix:/var/run/php5-fpm-owncloud.sock;
fastcgi_index index.php;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param SCRIPT_NAME $fastcgi_script_name;
}

}


and this is the one for rompr:

server {
listen 80;

access_log /var/log/nginx/access_log_www;

server_name rompr;

location /rompr {

root /var/www/rompr;
index index.php;

}


location ~ \.php$ {
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_pass unix:/var/run/php5-fpm-rompr.sock;
fastcgi_index index.php;
include fastcgi_params;
}

}


If I have a look at the error.log messages:

2014/05/04 07:27:32 [crit] 22455#0: *1 connect() to unix:/var/run/php5-fpm-rompr.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.1.37, $
2014/05/04 07:27:39 [error] 22455#0: *1 "/var/www/rompr/rompr/index.php" is not found (2: No such file or directory), client: 192.168.1.37, server: rompr, request: "GET /rompr/$
2014/05/04 07:27:49 [crit] 22455#0: *1 connect() to unix:/var/run/php5-fpm-rompr.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.1.37, $
2014/05/04 07:33:38 [error] 22455#0: *6 "/var/www/rompr/rompr/index.php" is not found (2: No such file or directory), client: 192.168.1.37, server: rompr, request: "GET /rompr/$
2014/05/04 07:34:52 [crit] 22455#0: *7 connect() to unix:/var/run/php5-fpm-rompr.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.1.37, $


So there seems to be a problem wih the directory because of the doubled "rompr", but also for accessing the "cloud" page since the first two error messages belong to the try for accessing the "cloud"page.

Is there something I could try or to modify in my config-files?

Thanks for help!

Viewing all articles
Browse latest Browse all 4759

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>