Tag Info

New answers tagged

0

You can reconfigure nginx to listen on a diffrent port number; I had faced a similar issue with Apache and nginx listening to the same port number (:80) sudo vim /etc/nginx/sites-available/default Change all port :80 to :8000 or another unused port number. Then check if the configuration is correct and restart nginx as follows: sudo /etc/init.d/nginx ...


0

If you want the execution errors of a script, that's configured on /etc/php5/fpm/php.ini. If you want errors on a log file, edit php.ini : display_errors = off error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT error_log = /path/to/some/file.log If you want them on the browser, edit php.ini : display_errors = on error_reporting = E_ALL ...


1

Basically, re-compiling the source is as easy as outlined in this code snippet on github, which mainly is making sure that the paths are correct for Ubuntu. Here is a short overview on which paths are important for ubuntu: ./configure --prefix=/etc/nginx \ --sbin-path=/usr/sbin/nginx \ --conf-path=/etc/nginx/nginx.conf \ ...


0

I didn't try it, but I think a redirection should work. Try adding this after the server block where you configure the SSL connection on the IP : server { listen 443; server_name *; return 301 http://$http_host$request_uri; }



Top 50 recent answers are included