Simple reverse proxy - 520 bad gateway
Jason In North Hollywood
nohojason at gmail.com
Fri Mar 17 01:34:17 UTC 2017
Hi Maxim - Thanks!
I found my error - even though I had SELinux on permissive, it was still
blocking. I though permissive allowed, but with logging.
BR
On Thu, Mar 16, 2017 at 9:06 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:
> Hello!
>
> On Thu, Mar 16, 2017 at 10:39:19AM +0800, Jason In North Hollywood wrote:
>
> [...]
>
> > Error in the log is:
> >
> > 2017/03/15 22:04:27 [crit] 8647#0: *11 connect() to 10.1.1.1:8080 failed
> > (13: Permission denied) while connecting to upstream, client:
> > 112.xxx.xxx.xxx, server: sub.domain.com, request: "GET /link1/
> HTTP/1.1",
> > upstream: "http://10.1.1.1.1:8080/link2/", host: "sub.domain.com"
> >
> > whats a bit strange looking is the GET /link1/ - as this this should not
> be
> > the link in the final upstream URL - it should not be trying to get this
> > link.
>
> The "request: ..." string in the error message is the original
> request as got from the client. It is to be used to identify the
> original request which caused the error.
>
> The upstream server and corresponding URI can be found in the
> "upstream: ..." string in the error message.
>
> --
> Maxim Dounin
> http://nginx.org/
> _______________________________________________
> 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/20170317/0a9e656c/attachment.html>
More information about the nginx
mailing list