Welcome! Log In Create A New Profile

Advanced

Re: Simple reverse proxy - 520 bad gateway

Maxim Dounin
March 16, 2017 09:08AM
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@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Simple reverse proxy - 520 bad gateway

Jason In North Hollywood March 15, 2017 10:40PM

Re: Simple reverse proxy - 520 bad gateway

Maxim Dounin March 16, 2017 09:08AM

Re: Simple reverse proxy - 520 bad gateway

Jason In North Hollywood March 16, 2017 09:36PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 177
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready