KB: Altium Enterprise Server Network Requirements
Updated: 九月 22, 2026
Altium On-Prem Enterprise Server
Altium On-Prem Enterprise Server (AES) requires specific network ports and services to be available for client connectivity, internal service communication, and optional integrations. In environments using firewalls, proxies, or network segmentation, proper configuration of these ports is essential to ensure reliable operation. This article identifies which ports must be accessible to clients, which ports should remain restricted to the local server, and how proxy settings are supported in AES deployments.
概览
Altium On-Prem Enterprise Server (AES) requires specific network ports and services to be available for client connectivity, internal service communication, and optional integrations. In environments using firewalls, proxies, or network segmentation, proper configuration of these ports is essential to ensure reliable operation. This article identifies which ports must be accessible to clients, which ports should remain restricted to the local server, and how proxy settings are supported in AES deployments.
Solution Details
Important: For an overview of network requirements across Altium products and links to detailed deployment-specific guidance, see KB: Network Requirements for Altium Products.
Altium On-Prem Enterprise Server (AES) — On-Premise Server Ports
If hosting AES on-premise, the following ports will be bound (used), and also listening to inbound traffic (from external sources in the first table). They are divided into client-facing (network) ports and local-only (localhost) ports.
Client-Facing Ports (AES ↔ AD Clients)
| Port | Protocol | Purpose | Notes |
|---|---|---|---|
| 9785 | TCP (HTTPS) | Primary AES communication | Required; modern AES traffic, including Git, uses this port. This 9785 port is the default option, but configurable in the installer (e.g. 443) |
| 9780 | TCP (HTTP) | AES HTTP communication | Localhost HTTP binding is mandatory for internal AES services. External (network) access on this port is optional if HTTPS-only is enforced. |
| 4649 | TCP | WebSocket communication | Required for real-time notifications. |
| 9090 | TCP | gRPC (PLM Connector SDK) | Bound by EIS for potential gRPC communication with the PLM Integration SDK PLM Integration SDK. Required only if using PLM integrations via the Connector SDK. |
Local-Only Ports (Localhost — Do Not Expose to Network)
| Port | Protocol | Purpose | Notes |
|---|---|---|---|
| 9791 | TCP | Synchronization service | Local only; restrict to localhost. Not required on the network firewall. |
| 3050 | TCP | Firebird database server | Restrict to localhost only; should not be exposed to the network. |
| 3690 | TCP | SVN version control | Removed in AES 8.1.3+. Only required for versions below 8.1.3. Legacy SVN protocol. |
| 9200, 9300 | TCP | Elasticsearch |
Proxy Server Support
- AES supports proxy configuration via
LocalVault.ini. All required URLs are listed in this file at the default installation path:C:\Program Files (x86)\Altium\[AES or NEXUS Server]\ - Known issue (fixed in AES 7.2.5+): PartCatalog service previously bypassed proxy settings from
LocalVault.ini. - PAC (Proxy Auto-Configuration) is not supported at this time.