Create a gist now

Instantly share code, notes, and snippets.

The nginx server configuration file needed to host the MirrorMirror application
server {
listen 80;
server_name localhost;
root /home/pi/projects/MirrorMirror/public;
index index.html index.htm index.php;
charset utf-8;
location / {
try_files $uri $uri/ /index.php?$query_string;
}
location = /favicon.ico { access_log off; log_not_found off; }
location = /robots.txt { access_log off; log_not_found off; }
access_log off;
error_log /var/log/nginx/myapp-error.log error;
sendfile off;
client_max_body_size 100m;
location ~ \.php$ {
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_pass unix:/var/run/php5-fpm.sock;
fastcgi_index index.php;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_intercept_errors off;
fastcgi_buffer_size 16k;
fastcgi_buffers 4 16k;
}
location ~ /\.ht {
deny all;
}
}
@patm189
patm189 commented May 13, 2016 edited

I've pasted this into sudo nano /etc/nginx/sites-available/mirror.conf but, I am unable to activate configuration when inputting the below.

sudo ln -s /etc/nginx/sites-available/mirror.conf /etc/nginx/sites-enabled/mirror.conf sudo service nginx reload

Error reads: ln: target 'reload' is not a directory. Any idea what I'm doing wrong?

@kischtof

I've exactly the same error : "ln: target 'reload' is not a directory"
Could you help us ?

@brenzenb
brenzenb commented May 17, 2016 edited

I think you want to break that into two separate commands.
sudo ln -s /etc/nginx/sites-available/mirror.conf /etc/nginx/sites-enabled/mirror.conf
sudo service nginx reload

That error message is because the symlink command, ln -s, is trying to create a symlink to reload, which is not a command. You accidentally created symlinks for the sudo, service, and nginx commands/utilities.

@Anool
Anool commented Jun 3, 2016

Hi, Trying to build a MirrorMirror and facing an issue. Hope you can help.

Running
sudo service nginx reload
results in
[FAIL] Reloading nginx configuration: nginx failed!

I tried
sudo nginx -c /etc/nginx/nginx.conf -t
and it shows this
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: [emerg] socket() [::]:80 failed (97: Address family not supported by protocol)
nginx: configuration file /etc/nginx/nginx.conf test failed

Any tips ? (for a "Not a software guy")

@Anool
Anool commented Jun 4, 2016

Alright, I got nginx to run by editing
/etc/nginx/sites-available/default

and commenting out the IPv6 line
listen [::]:80 default_server;

and nginx runs now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment