Re: Serving website with Apache, with Nginx as interface?

On Tue, May 17, 2016 at 1:37 PM, Francis Daly wrote: > On Mon, May 16, 2016 at 08:50:44AM -0400, Alex Hall wrote: > > Hi there, > > > Well, it seems to be working now, and I'm thoroughly embarrassed about > it. > > The Nginx/Apache setup is fine, and has been, it seems. > >

Re: Serving website with Apache, with Nginx as interface?

On Mon, May 16, 2016 at 08:50:44AM -0400, Alex Hall wrote: Hi there, > Well, it seems to be working now, and I'm thoroughly embarrassed about it. > The Nginx/Apache setup is fine, and has been, it seems. Thanks for reporting that result -- it'll help the future reader of the mailing list

Re: Serving website with Apache, with Nginx as interface?

Hi all, Well, it seems to be working now, and I'm thoroughly embarrassed about it. The Nginx/Apache setup is fine, and has been, it seems. The OST error was rather cryptic, but once I finally found where in the OST code it was being generated, I discovered that it was likely a database failure. I

Re: Serving website with Apache, with Nginx as interface?

> On May 14, 2016, at 05:19, Francis Daly wrote: > > On Fri, May 13, 2016 at 01:24:57PM -0400, Alex Hall wrote: > > Hi there, > >> It's as though the proxy weren't working properly at all. >> I have it set up in a location: >> >> upstream apache2Redirect { >> server

Re: Serving website with Apache, with Nginx as interface?

Alex Hall Wrote: --- > upstream apache2Redirect { > server 127.0.0.1:8080; > } > > location / { > proxy_set_header Host $host; > proxy_pass http://apache2Redirect; > } Browser(get localhost:8080) -> osticket (return responses with

Re: Serving website with Apache, with Nginx as interface?

As a quick update, setting proxy_set_header Host $host; seems to have gotten the URL working, but OSTicket is still giving me the same error I was getting when I was serving it with Nginx directly. Worse, the Apache2 access log shows none of my recent attempts to access the site, though it does

Re: Serving website with Apache, with Nginx as interface?

Sorry, backend1 its upstream in nginx configuration upstream backend1 { #ip of Apache back-end server 192.168.0.1:8080; } 2016-05-13 1:59 GMT+03:00 Alex Hall : > Thanks! I followed you, until the proxy_pass. What is backend1, and where > is it defined? I know it's

Re: Serving website with Apache, with Nginx as interface?

Thanks! I followed you, until the proxy_pass. What is backend1, and where is it defined? I know it's something you made up, but how does it know about Apache, or Apache about it? > On May 12, 2016, at 17:56, Yuriy Medvedev wrote: > > Hi, you can use vhost in Apache and

Re: Serving website with Apache, with Nginx as interface?

Hi, you can use vhost in Apache and configure proxy_pass in nginx configuration For apache2 somthing like that ServerName foo.bar DocumentRoot /home/sites/ Order deny,allow Allow from all ErrorLog /home/sites/logs/apache_error.log CustomLog

Re: Serving website with Apache, with Nginx as interface?

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

Serving website with Apache, with Nginx as interface?

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