Publishing a project or content (such as Dashboard) to Exploratory Server fails with HTTP 413 "Payload Too Large”

Issues
#1

If you’re trying to publish a large project or content (such as a Dashboard) to your Exploratory Server (On-Premise), you might encounter the following error message:

HTTP 413 "Payload Too Large”

This error message indicates that the size of the project you’re trying to publish exceeds the maximum allowed payload size of your server. Here is how to fix it.

1. Check ‘default.conf’.

Open the default.conf file under the exploratory directory of your On-Premise server installation and make sure that there is a parameter client_max_body_size with the value 0. This parameter defines the max upload file size, and 0 means unlimited. If there is no such parameter, or it has a parameter but the value is rather than ‘0’, please update it. Here is an example.

server {
    listen       443;
    server_name  localhost;
    ssl on;
    ssl_certificate    /etc/nginx/ssl/fullchain.pem;
    ssl_certificate_key    /etc/nginx/ssl/privkey.pem;
    client_max_body_size 0;

If you updated the parameter, restart the Exploratory Server (On-Premise) and try it again.

2. Check out the load balancer.

If the default.conf file looks good but you still have a problem, the problem could be coming from a load balancer or similar system that blocks large requests.

  1. Check if there is a load balancer or similar system between the Exploratory Server and your browser.
  2. If there is, ensure it’s configured to allow large requests. You may need to consult your load balancer documentation or contact your IT department for assistance.
1 Like