Legacy Knowledge Base
Published Sep. 10, 2025

'Connection reset by peer' when uploading files

Written By

Aurél Förstner

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • You are encountering the following exception in the logs:
    java.io.IOException: Connection reset by peer
  • Users cannot upload files and errors like the following are printed (some examples):
    WARN [UploadServletRequestImpl:245] Unable to parse upload request: Processing of multipart/form-data request failed. Connection reset by peer
    WARN [SecurityPortletContainerWrapper:414] User XXXX is not allowed to access URL https://mydomain.com/path/ and portlet com_liferay_document_library_web_portlet_DLAdminPortlet: User XXXX did not provide a valid CSRF token for com.liferay.portlet.SecurityPortletContainerWrapper

Environment

  • Liferay DXP 7.0
  • Liferay DXP 7.1
  • Liferay DXP 7.2
  • Liferay DXP 7.3
  • Liferay DXP 7.4
  • Liferay DXP Quarterly Releases

Resolution

  • Connection reset by peer suggests that the TCP connection was broken by the other end or something during the network traffic.
  • There is usually a network hardware, such as the load balancer, firewall, router, network security, or switch, which has an idle timeout for connections and will reset connections that are inactive for a period of time, or even if you abruptly abort the action.
  • To determine if intermediate components are contributing to the problem, bypass them by accessing the application server directly.
Did this article resolve your issue ?

Legacy Knowledge Base