Adding a new protected machine results in a blank screen

{kb-symptom}

{code}upstream sent invalid chunked response while reading upstream{code}

{kb-cause}
This issue is caused by a running Nginx reverse proxy on the Backup Manager system.
By default, Nginx uses Http 1.0 when functioning as a reverse proxy. The "Transfer-Encoding: chunked" response in the R1Soft Backup Manager headers, requires Http 1.1 when no chunked data is sent.


{kb-resolution}
Configuring Nginx to use Http 1.1, by adding the lines below, resolves this issue.
{code}proxy_http_version 1.1;<br> proxy_set_header Connection "";{code}

h6. Depending on how Nginx is being used, the configuration change may be added to one of the following conf files:

h4. *Global Configuration :*

Add the following lines to the http{} section of the primary configuration file : /etc/nginx/nginx.conf
{code}# Chunked response handling   
proxy_http_version 1.1;
proxy_set_header Connection "";{code}

h4. *Server Block Configuration* (installed from the official Nginx repository) :

Add the following lines to the site config of the virtual host, located&nbsp; here : /etc/nginx/conf.d/

_Example:_
{code} # R1Soft
location / {
proxy_pass http://127.0.0.1:8080;
...
proxy_http_version 1.1;
proxy_set_header Connection "";
}{code}

h4. *Server Block Configuration* (installed from Debian or Ubuntu Repositories) :

Add the following lines to the site config of the virtual host, located&nbsp; here : /etc/nginx/sites-available/
(configs created in this folder are typically enabled by symlinking to /etc/nginx/sites-enabled/ )

_Example:_
{code} # R1Soft
location / {
proxy_pass http://127.0.0.1:8080;
...
proxy_http_version 1.1;
proxy_set_header Connection "";
}{code}
NOTE: After adding the config lines to the appropriate location for your installation, nginx will need to be reloaded with :
{code} # nginx -s reload{code}


{kb-related-articles}