This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Network destinations
The external addresses a Citrix SecurSpaces™ deployment must reach, for firewall rules and air-gapped planning.
Version numbers on this page are for the 2026.9.0 release. Substitute the version you are installing.
Summary
| Destination | Purpose | Needed |
|---|---|---|
api.enterprise.strong.network:443 |
License verification and renewal | Continuously, unless you use an offline license |
| Docker Hub | The Strong Installer image | At install and upgrade time |
europe-docker.pkg.dev and regional mirrors |
Helm chart and container images | At install and upgrade time |
License server
| Item | Value |
|---|---|
| Address | api.enterprise.strong.network |
| Port | 443 |
| Purpose | Online license verification and renewal |
During installation the platform contacts the license server to validate the license and to issue a temporary token for the container image registry.
You can supply a signed license instead, by setting platform.license in the Helm values to a base64-encoded
license. It is applied automatically on deploy and upgrade.
Note:
For air-gapped environments, either allow the SecurSpaces controller to reach the license server through your firewall, or request an offline license for fully disconnected operation. See License.
Installer image
| Item | Value |
|---|---|
| Source | Docker Hub |
| Image | strongnetwork/strong_installer:2026.9.0 |
Helm chart
| Item | Value |
|---|---|
| Source | Google Artifact Registry |
| Primary | europe-docker.pkg.dev/strong-network-release/charts/ninjahchart:2026.9.0 |
| Mirrors |
us-docker.pkg.dev, asia-docker.pkg.dev
|
Container images
| Item | Value |
|---|---|
| Source | Google Artifact Registry |
| Primary | europe-docker.pkg.dev/strong-network-release/images |
| Mirrors |
us-docker.pkg.dev, asia-docker.pkg.dev
|
Choose the mirror closest to your cluster with the --source-registry-region flag. See
SDS CLI reference.
Service images
| Image |
|---|
cloud_editor_sidecar_proxy:2026.9.0 |
sn_enterprise_bundle:2026.9.0 |
Workspace image
| Image |
|---|
ws-images/cloud_editor_generic:2.3.8 |
This is the only workspace image the installer pushes. The tag comes from the installer’s built-in default,
which you can override with the -w or --workspace-image-tag flag.
Additional workspace images
Citrix publishes further workspace images and example image definitions, covering IDEs and language toolchains beyond the default image.
| Source | Address |
|---|---|
| Example image definitions | github.com/strong-network/images |
| Prebuilt images | hub.docker.com/u/strongnetwork |
Important:
The installer does not push these images. It pushes only the service images and the single workspace image listed above. To use an additional image in an air-gapped deployment, pull it and push it to your own registry yourself, then add it as a container image.
See Container images for adding an image to a project, and Container image requirements for what an image must provide.
Related information
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.