Tag Info

Hot answers tagged

3

There is nothing special in the server log which shows a problem at the site of nginx. But, you description clearly indicates a problem in the clients network, i.e. only clients in the same network are affected all clients in the same network are affected if client connects to another network while experiencing the problem, the problem no longer occurs ...


3

You can use AWS API Gateway (documemtation). API Gateway helps developers deliver robust, secure and scalable mobile and web application backends. API Gateway allows developers to securely connect mobile and web applications to business logic hosted on AWS Lambda, APIs hosted on Amazon EC2, or other publicly addressable web services hosted inside or ...


1

monit doesn't accept shell scripts with start program/stop program. You need to write like this: check process nginx with pidfile /opt/nginx/logs/nginx.pid start program = "/bin/sh -c '/etc/init.d/nginx restart; touch /var/www/apps/myapp/tmp/restart.txt'" stop program = "/etc/init.d/nginx stop"


1

Run /usr/sbin/nginx -s reload See http://wiki.nginx.org/CommandLine for more command line options.


1

You need to define a default virtual host in nginx, which will deny requests. server { listen 80 default_server; server_name _; location / { deny all; } }


1

Looks to me like your https blocks need server names specified too e.g server { listen 443; server_name bar.domain.com; ssl on; ssl_certificate [path_bar]/cacert.pem; ssl_certificate_key [path_bar]/privkey.pem; root [path]/bar; }


1

I would use this: server { listen 80; server_name www.example.com example.com; # this is default server. ... } server { listen 80; server_name www.*; # here www.*.example.com .. } server { listen 80 default_server; return 301 http://www.$host$request_uri; }



Only top voted, non community-wiki answers of a minimum length are eligible