Skip to main content
These ports must be open in order to make Zylon work:
  • 80: Default http port. Only used during SSL certification generation with https://letsencrypt.org/. If you intend to provide your own SSL certificates this port is optional.
  • 443: Default https port. Used for the rest of traffic.
Map traffic to ports 80 and 443
  • Zylon Port 80 ↔ Host port 80
  • Zylon Port 443 ↔ Host port 443
Additional / Temporarily open ports:
  • 22: SSH port. During installation and initial setup, this port should be open so your IT team or Zylon operations team can help you get the application running. As a general security practice, you should close this port as soon as the installation is complete.
  • 6443: Kubernetes API service. To help our team further debug your installation, you can also open port 6443 temporarily. All connections to the Kubernetes service are authenticated, having this port open does not put your data at risk. During the time the port is open it will allow Zylon Operations team to access your machine.

DNS configuration

The following requirements are needed for Zylon to work:
  • Choose a domain for Zylon, for example: zylon.company.com. A domain name is required for a secure connection.
  • Configure DNS entries so zylon.company.com point to the machine that has Zylon installed
After you have installed Zylon in your environment some extra steps need to be performed to be able to access it over the internet (or VPN). Take this points into consideration:
  • The web application is running locally in the user’s web browser.
  • The server is running in the machine where it was installed.
  • You MUST configure SSL/HTTPS yourself or delegate Zylon to automatically do it for you
  • Do NOT activate SSL redirect unless you plan to provide custom SSL certificates.
During the installation, a domain was chosen to be the entry point of Zylon. This will be used as the host parameter in the configuration (for example zylon.company.com)

Example DNS configuration

Zylon is installed in a machine with IP 32.41.12.123 . Your DNS entry could look like the following:

Subdomains

Some Zylon features are served from their own subdomain of your Zylon domain: For each feature you use, create a DNS record for its subdomain that points to the same machine as your Zylon domain. A wildcard record such as *.zylon.company.com covers all of them.

SSL certificates for subdomains

This section is only necessary if you are not using Let’s Encrypt certificates
With Let’s Encrypt, the certificates for the subdomains are issued automatically. With manual SSL certificates, each subdomain needs its own Kubernetes secret, with a certificate that covers the subdomain, either by name or with a wildcard such as *.zylon.company.com. Prepare the tls.crt and tls.key files in the same way as for your Zylon domain.
  • n8n: follow n8n SSL certificates configuration.
  • Sandbox app links: create the zylon-tls-sandbox-exec secret in the opensandbox namespace, not in zylon. Do this after Zylon is installed and after running sudo zylon-cli sync for any pending configuration changes. You don’t need to sync again afterwards: the sandbox ingress picks up the secret within a few seconds.
Certificate renewal must be done manually: run the same commands with the updated certificate files. If a sandbox app link shows a certificate warning after a zylon-cli sync or an upgrade, check that the secret still exists and create it again if it doesn’t.