Serving website with Apache, with Nginx as interface?

[Sven Kirschbaum]

Hello,

let Apache listen on a different port and create two server blocks in
nginx, one for each site. Then configure nginx to proxy the requests to sd2
to apache.
Just google "nginx reverse proxy" and you will find much information.

Yours sincerely
Sven Kirschbaum

2016-05-12 23:34 GMT+02:00 Alex Hall <ahall at autodist.com>:

> Hello all,
> Here's what I'm trying to do. I have two sites, sd1.mysite.com and
> sd2.mysite.com. The fun part is that sd1 is a Flask app, served by Nginx.
> However, sd2 is OSTicket, which must be served by Apache, it seems. Of
> course, Apache and Nginx can't listen to port 80 at the same time, and as
> this is a subdomain on a local, Windows DNS, I can't make sd2.mysite.com
> point to myip:8080 or anything like that.
>
> Thus, my best option appears to be this: Nginx listens to all incoming
> traffic on 80. If the request is for anything to do with sd1, it handles it
> just like it does now. However, if the request is for sd2, Nginx somehow
> hands off the request to Apache, then returns what Apache gives it back to
> the user.
>
> I've heard that people use Apache and Nginx together, but I haven't found
> anyone who uses them to serve two subdomains, with Nginx as the "gateway"
> and handler of one subdomain, and Apache as the handler for the other
> subdomain. Is there any way to do this? Am I even making sense? Thanks for
> any ideas anyone has.
>
> --
> Alex Hall
> Automatic Distributors, IT department
> ahall at autodist.com
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160512/17fa5974/attachment.html>