Skip to main content
Sign in

Resolve Maven SSL connection error when starting App Studio Enterprise behind a proxy

  • Updated

Issue

When starting App Studio Enterprise using the app-studio start -f command, the application logs indicate a connection failure with the message:

javax.net.ssl.SSLConnection: Connection reset

This occurs even after editing Maven configuration files. The application attempts to download dependencies from https://repo1.maven.org, but the connection is blocked or reset, often in environments behind a corporate proxy.

 

Diagnosis

This issue typically occurs when:

  • App Studio is deployed in a corporate environment behind a proxy or firewall

  • Maven fails to route outbound HTTPS requests to public repositories due to missing or misconfigured proxy settings

  • SSL errors such as Connection reset appear early during App Studio startup, and dependency downloads stall

You can confirm the issue by reviewing the App Studio logs (e.g., app-studio-8080-console.log) and identifying errors associated with Maven artifact downloads.

 

Environment

  • App Studio Enterprise 4.11.0

  • Fusion 4.2.6

  • Windows Server 2019

  • Maven 3.8.1

  • Java 8

  • Node.js 14.17.0

 

Cause

The Maven client used by App Studio is unable to access public repositories due to a lack of proxy configuration. Maven must be explicitly configured to route traffic through the corporate proxy using a settings.xml file.

 

Resolution

Configure Maven proxy settings

  1. Locate the settings.xml file used by Maven. This may be in one of the following locations:

    • app-studio/bin/settings.xml

    • ${user.home}/.m2/settings.xml (user-specific)

  2. Edit the settings.xml file and add a <proxy> block under the <proxies> section. For example:

<settings>
  ...
  <proxies>
    <proxy>
      <id>corporate-proxy</id>
      <active>true</active>
      <protocol>http</protocol>
      <host>proxy.example.com</host>
      <port>8080</port>
      <username>your-username</username>
      <password>your-password</password>
      <nonProxyHosts>localhost|127.0.0.1</nonProxyHosts>
    </proxy>
  </proxies>
  ...
</settings>

  1. If you maintain both an app-studio/bin/settings.xml and a user-level ${user.home}/.m2/settings.xml, merge the proxy block into the latter to ensure it's used globally.

  2. Optionally, verify your system-wide proxy settings in Windows, especially if you’re behind a VPN or firewall.

Validate the configuration

  • Restart App Studio using: app-studio start -f

  • Monitor the logs (app-studio-8080-console.log) to confirm that Maven no longer fails to reach repo1.maven.org.

  • If errors persist, capture network traffic using a packet sniffer (e.g., Wireshark) to identify blocked requests, and consult with the internal IT or network security team for firewall adjustments.

 

Additional notes

  • If no proxy block is configured, or if credentials are incorrect, Maven will silently fail to connect to the repository and throw SSL or timeout errors.

  • Ensure proxy credentials are kept secure and updated when changed in your organization.

Related articles

Powered by Zendesk