Knowledge Base›Troubleshooting›Veeam API Proxy times out connecting to a platform that uses a non-default HTTP port
Veeam API Proxy times out connecting to a platform that uses a non-default HTTP port
Source and classification
- Source: Site case from the Veeam integration Technical Support group.
- Classification: Configuration and environment issue.
- Confirmation basis: The site used HTTP and a non-default ZSphere access port. API Proxy lacked the actual platform address, port, and context path, so its Java service timed out connecting to the platform. An in-place API Proxy installation with the actual parameters restored service.
- Internal tracking: No related Jira.
Issue metadata
- Issue ID: None.
- Component/product: ZSphere, Cloud, and Veeam API Proxy.
- Status: Resolution available.
- Priority/severity: General.
- Affected versions: Confirmed in API Proxy 1.0.x site environments; for other versions using a non-default platform address, check actual configuration.
- First fixed version: Not applicable; correct platform-access parameters resolve this issue.
- Confirmation date: June 5, 2026.
Sign in to view the rest of this article, plus more troubleshooting and solution know-how.
Sign in