Skip to content

Change the ports

The three HTTPS interfaces have independent ports, configurable in the component YAML files:

Interface YAML key Default port Example below
Frontend smartagt.http.server.port in the Frontend YAML 9000 19000
Public API smartagt.http.public.port in the Backend YAML 8000 18000
AI Gateway smartagt.gateway.server.port in the Backend YAML 8001 18001

Changing a port keeps the certificates valid: their SAN covers the DNS name or IP address, not the port. To also change certificates, see Install your certificates.

Prerequisites

  • Installed components and access to their YAML files.
  • Chosen ports available on the listening addresses, between 1 and 65535, and permitted by the operating system for the service accounts.
  • Access to firewall rules and any proxies or load balancers.

Back up the YAML files before editing. The example changes all three ports; apply only the changes you need and merge the keys into the existing blocks.

Procedure

1. Edit the YAML files

In /app/config/backend/smartagt-backend-core.yaml:

smartagt:
  http:
    public:
      port: 18000
  gateway:
    server:
      port: 18001

In /app/config/bff/smartagt-bff-core.yaml:

smartagt:
  http:
    server:
      port: 19000
    backend:
      base_url: "https://localhost:18000"
    cors:
      allow_origins:
        - "https://smartagt.example.test:19000"

On Windows, the files are under C:\app\config\backend\ and C:\app\config\bff\. Keep the listening address and TLS settings already suited to your installation.

backend.base_url identifies the Public API used for enrollment and internal link discovery. If it is on another server, replace localhost with its hostname reachable from the Frontend. If its public port stays unchanged behind a load balancer, keep this URL.

The CORS origin matches the address seen by the browser. If a reverse proxy stays on 443, keep https://smartagt.example.test, even if the Frontend moves to 19000 behind it. If direct access changes, update the origin while keeping any other addresses still needed: CORS.

Expected result: each chosen port is declared once, in the correct component YAML.

2. Update access and restart

Affected element Action
Firewall Allow the new ports only for their intended clients.
Proxy or load balancer Update node and health check ports. An internal port can change without changing the public port.
Public Frontend address If it changes, update the installation's public URL and user access links. For SSO, also check the Backend origin list and the provider's redirect URLs: CORS.
Public API clients Update their URLs with its new port, as well as http.backend.base_url on the affected Frontends.
AI Gateway clients If the public address changes, update the Public URL in AI Factory > AI Gateway, as well as the URLs of connected tools.

Restart the modified services: Operations. In a cluster, apply the YAML files to the affected nodes and coordinate their restart with port changes in the load balancers.

Internal interfaces 8010 and 8011 have separate configuration. This procedure does not change them: see Configuration.

3. Verify

Open the Frontend at its new address in Chrome and Edge: the certificate must be trusted, and login, page reload and logout must work. Then test an authenticated request to the Public API and AI Gateway, using their new addresses with TLS validation enabled.

Check that the services no longer listen on their previous ports, then remove unused old network rules. If the page loads but login is refused, check the CORS origin.

To restore the previous ports, restore the backed-up YAML files, public addresses, client URLs and network rules. Restart the affected services and repeat these checks.