Error 512 after nginx setup

Francis Daly francis at
Fri Mar 20 21:39:17 UTC 2020

On Sun, Mar 15, 2020 at 08:58:38PM +0200, Adrian Vidican wrote:

Hi there,

> I setup Nginx on my Ubuntu 16.04 server to point my domain (using cloudflare) to my server where <> is installed.

Is there any evidence (logs, tcpdump) that the request got to your nginx
in the first place?

If not -- you have something outside of nginx to adjust, so that the
request gets that far.


>     location / {
>         proxy_pass <>;
>         proxy_set_header Host $http_host;
>         proxy_http_version 1.1;
>         proxy_set_header X-Forwarded-Proto $scheme;
>         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
>         proxy_redirect <> <>;
>     }

> There's no error of Nginx but I've get 512 in browser.

Does your upstream port-2045 service return the 512 message?

(512 is not a standard http response code. So something must be creating
it specially.)

What response do you get if you use "curl -i" (or "curl -v") to make
the request? That is less likely to hide important information.


Francis Daly        francis at

More information about the nginx mailing list