<div dir="ltr"><div>Hi all,<br></div>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-granted privileges to my OST user, and suddenly the installation completed.<br><br>Thus far, everything is running normally. I guess the lesson is to always check your DB user privileges, and hope OST puts in better error messages.<br><br>Thanks for the help, everyone; this taught me a lot, about Nginx configuration, upstream contexts, and so on. Even if the final answer was my own mistake in privilege settings, I couldn't have done the rest of the setup without the help of the list. I'll likely be back with more questions, but for now, everything seems stable and okay.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 14, 2016 at 7:32 AM, Alex Hall <span dir="ltr"><<a href="mailto:ahall@autodist.com" target="_blank">ahall@autodist.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On May 14, 2016, at 05:19, Francis Daly <<a href="mailto:francis@daoine.org">francis@daoine.org</a>> wrote:<br>
><br>
> On Fri, May 13, 2016 at 01:24:57PM -0400, Alex Hall wrote:<br>
><br>
> Hi there,<br>
><br>
>> It's as though the proxy weren't working properly at all.<br>
>> I have it set up in a location:<br>
>><br>
>> upstream apache2Redirect {<br>
>> server <a href="http://127.0.0.1:8080" rel="noreferrer" target="_blank">127.0.0.1:8080</a>;<br>
>> }<br>
>><br>
>> location / {<br>
>> proxy_set_header Host $host;<br>
>> proxy_pass <a href="http://apache2Redirect" rel="noreferrer" target="_blank">http://apache2Redirect</a>;<br>
>> }<br>
>><br>
>> My understanding is that the / will match everything, from /index.html to<br>
>> /images/small/235.jpg. Is that not the case? Do I need to do something to<br>
>> my location block, by chance?<br>
><br>
> If the "location" you show above is the entire content of your server{}<br>
> block, then all requests that get to nginx should be handled in it.<br>
><br>
> If you have more config that you are not showing, then possibly that<br>
> extra config is interfering with what you want to do.<br>
><br>
</span>Sorry I should have said. Yes, that's all there is to my config file. I wanted every request to go to Apache, including any subdirectories.<br>
<span class="">><br>
> The best chance of someone being able to help, is if you can include<br>
> very specific details about what you do, what you see, and what you<br>
> expect to see instead.<br>
<br>
</span>The problem is that the error I'm seeing is in OSTicket. All I can say is that the OST forums aren't any help, that I don't see the error on Apache under Windows, and that I do see it under this configuration. It's the exact same error I saw when serving OST with Nginx directly, which is why I think the proxy isn't working correctly. Plus, I don't see the access to the OST pages in the Apache access log after 11:14, despite trying it all day yesterday. Nginx registers them, but not Apache. Yet, if I stop Apache, I get a 502 when trying to pull up OST.<br>
<span class="">><br>
> If you use the "curl" command-line tool instead of a normal browser, you<br>
> can make one request and see the full response. If you know what response<br>
> you expect, you can compare it to the response that you actually get.<br>
><br>
><br>
> curl -v <a href="http://ngninx-server/OSTicket/" rel="noreferrer" target="_blank">http://ngninx-server/OSTicket/</a><br>
><br>
> (or whatever url you have set things up at).<br>
><br>
> Without knowing what you do want to see, I'm pretty sure that you do<br>
> not want to see "127.0.0.1" or "8080" anywhere in the response.<br>
<br>
</span>Curl is a good idea. I'll try that Monday when I'm back in the office (this is an intranet site, so I can't test it from home, though I can ssh into the server).<br>
<div class="HOEnZb"><div class="h5">><br>
> Good luck with it,<br>
><br>
> f<br>
> --<br>
> Francis Daly <a href="mailto:francis@daoine.org">francis@daoine.org</a><br>
><br>
> _______________________________________________<br>
> nginx mailing list<br>
> <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
> <a href="http://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div>Alex Hall<br></div>Automatic Distributors, IT department<br></div><a href="mailto:ahall@autodist.com" target="_blank">ahall@autodist.com</a><br></div></div>
</div>