ISPsystem.com Forums - Choose between Apache/Lighttpd/Nginx

ISPsystem.com Forums (http://forum.ispsystem.com//index.php)

- Feedback & Feature Requests (http://forum.ispsystem.com//forumdisplay.php?f=9)

- - Choose between Apache/Lighttpd/Nginx (http://forum.ispsystem.com//showthread.php?t=715)

Choose between Apache/Lighttpd/Nginx

isp manager pro should have a feature when we can set the default web server we want to use. So if we choose Nginx, then Apache will be completely disabled and only Nginx will be running.

You should have 3 options: Apache/Lighttpd/Nginx

All of isp manager pro's features should work 100% correctly on any of the 3 web servers.

ISPmanager works with Apache server. It is possible to install Nginx as front-end for proxying http requests.
Other configurations are not supported.

My feature request is to allow ISPmanager to work WITHOUT Apache server. So people can choose Apache or Nginx.

Quote:

Originally Posted by slava (Post 3271)

ISPmanager works with Apache server. It is possible to install Nginx as front-end for proxying http requests.
Other configurations are not supported.

Quote:

to allow ISPmanager to work WITHOUT Apache server

This is impossible, at least in the near future, at least it will not happen in the current major version (4.x).

by proxying http requests, do you mean static AND dynamic content? OR just static content?

Quote:

Originally Posted by slava (Post 3271)

ISPmanager works with Apache server. It is possible to install Nginx as front-end for proxying http requests.
Other configurations are not supported.

Static and dynamic content.

so what is apache used for then?

Quote:

Originally Posted by slava (Post 3383)

Static and dynamic content.

Quote:

so what is apache used for then?

1. ISPmanager core needs apache, because ispmgr runs through apache SSL port.

2. Nginx proxyng requests to apache and transfers static content, for example from nginx.conf

Code:

        server {

                listen 193.0.0.193:80;

                server_name example.com www.example.com;

                rewrite ^(/manager/.*)$ https://$host$1 permanent;

                location ~* ^/(webstat/|awstats|webmail/|myadmin/|manimg/) {

                        proxy_pass http://193.0.0.193:8080;

                        proxy_redirect http://example.com:8080/ /;

                        proxy_set_header Host $host;

                        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

                        proxy_set_header X-Real-IP $remote_addr;

                }

                location / {

                        proxy_pass http://193.0.0.193:8080;

                        proxy_redirect http://example.com:8080/ /;

                        proxy_set_header Host $host;

                        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

                        proxy_set_header X-Real-IP $remote_addr;

                }

                location ~* ^.+\.(jpg|jpeg|gif|png|svg|js|css|mp3|ogg|mpe?g|avi|zip|gz|bz2?|rar)$ {

                        root /home/web/data/www/example.com;

                        access_log /home/httpd-logs/example.com.access.log;

                        error_page 404 = @fallback;

                }

                location @fallback {

                        proxy_pass http://193.0.0.193:8080;

                        proxy_set_header Host $host;

                        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

                        proxy_set_header X-Real-IP $remote_addr;

                }

        }

Apache back-end listen port 8080 and execute php/cgi-scripts, nginx front-end listen http port 80 and send data to web-browser and proxying request for static content files directly.

2 Dewarregekdazy:
Create a new thread for your problem. This thread was closed.