SVN Failed to check out E175002: SSL peer shut down incorrectly

Article ID:212885737
1 minute readKnowledge base

Issue

org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /MY_REPO/!svn/vcc/default failed
...
Caused by: svn: E175002: SSL peer shut down incorrectly
▼

Environment

  • CloudBees Jenkins Enterprise

  • SVN

Resolution

This can be caused by:

  • Large files (>20mb) being committed.

  • Large commits.

  • Timeout on Server hosting SVN being too low (nginx, apache).

Fixes include:

  • Avoiding committing files larger than 20mb. Suggestion is to use something like Amazon S3 for this instead.

  • Splitting commits into smaller revisions.

  • Increasing timeout on HTTP Server (nginx, apache).

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.