Network and external connectivity
Shared outbound connectivity, external access, and responsibility requirements for Docker Compose and Kubernetes deliveries.
Connectivity requirementsThe product is not offline or air-gapped. Keep the documented outbound routes available for license heartbeat, signed usage metering, cloud billing, image delivery, and Telegram/MAX connectivity.
Shared network contract
Both delivery methods require these connections. Inbound ports and publication depend on the selected deployment method.
- License issuance and state control
- Signed usage counter and assigned message tariff
- Balance, billing, and access to the deployment package and updates
Outgoing connections
The destinations and ports match the current delivery contract in source control.
| Purpose | Destination address | Port | Protocol |
|---|---|---|---|
| Control panel, package download and license activation | massaccess.net | 443 | HTTPS |
| Image registry (install and upgrade) | gitlab.massaccess.net | 443 | HTTPS |
| Message translation (optional) | translate.api.cloud.yandex.net | 443 | HTTPS |
Method-specific requirements
After checking shared connectivity, open the requirements for the selected delivery method.