# How to Resolve Publish Failures for Large Content on On-Premise Server

**URL:** <https://community.exploratory.io/t/how-to-resolve-publish-failures-for-large-content-on-on-premise-server/3898>\
**Category:** Issues\
**Created:** [May 12, 2025, 5:49pm UTC](https://community.exploratory.io/t/how-to-resolve-publish-failures-for-large-content-on-on-premise-server/3898 "2025-05-12T17:49:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![user1](https://community.exploratory.io/user_avatar/community.exploratory.io/user1/32/11_2.png) [@user1](https://community.exploratory.io/u/user1)\
**Post date:** [May 12, 2025, 5:49pm UTC](https://community.exploratory.io/t/how-to-resolve-publish-failures-for-large-content-on-on-premise-server/3898/1 "2025-05-12T17:49:26Z")

</div>

## Problem

When attempting to publish large content such as charts, dashboards, etc, the publish process fails.

## Cause

It is possible that proxy server settings such as `http_proxy` and `https_proxy` are configured in the Docker environment where the Exploratory server is running. These settings might interfere with external network communication during the publish process.

## Solution

Follow the steps below to remove proxy settings from the Docker environment and resolve the publish failure.

1. **Check the Container ID**  
Run the `docker ps` command to check the container ID of the Exploratory instance. Example output:

2. **Check for Proxy Settings**  
Run `docker inspect <container_id>` and check the `Env` section under `Config`. If you see entries like the following, it means a proxy server is configured:

3. **Update `docker-compose.yml`**  
In the `docker-compose.yml` file, add the following 4 lines to the `environment:` section of each service (mongodb, exploratory, nginx, scheduler, rserve, webdav, agendash). If `environment:` does not exist, create it.

4. **Restart the Docker Containers**

5. **Verify Changes**  
Repeat steps 1 and 2 to confirm that proxy settings have been removed.
