How to Manage One Click App Domains and Public TCP/UDP Endpoints in xCloud

Updated November 16, 2026 · 9 min read

Summarize with:
Share:

One Click Apps installed from xCloud templates manage their domains on a dedicated Domain page. An app with one web interface has one domain. An app with several web interfaces (for example a main app and a separate admin console) gets one domain per interface, and they all move from demo to live domains together. To install one of these apps, see how to install multi-domain One Click apps in xCloud. Some apps also expose a non-web service, such as a game server or a sync service, on a public TCP or UDP port; xCloud lists those addresses on the app’s Credentials card. Database apps work the other way round: a new install stays private to the server unless you choose otherwise (see keep a database private or open it to the internet).

You can also send extra domains to a live app as redirect domains.

To install a new app, start with how to use One-Click App Templates. This guide covers what you do after the install.

Open the Domain page

  1. Open the One Click App’s site.
  2. In the sidebar, open Domain → Domain.

Apps without a web interface (data services such as a database) have no Domain page.

Site state Card title Button
Demo site Demo Site Domain Go Live
Live site Domain Save

For an app with several web interfaces, the page lists every interface by name. The one marked Primary is the app’s main interface.

Domain page of an xCloud One Click App with one demo domain per web interface

Move a demo app to live domains

A demo install runs on generated demo domains, one per web interface.

  1. On the Demo Site Domain card, click Go Live. The page switches to empty fields, one per interface.
  2. Enter a domain for every interface. Each needs its own hostname; you cannot reuse one hostname for two interfaces.
  3. Point an A record for each domain to your server. The page lists each record under Point an A record to your server, with the server’s IP address and a copy button.
  4. Click Verify My DNS. If verification fails right after you add the records, wait a few minutes for DNS to propagate and try again. See how to set up a DNS record for an xCloud server.
  5. Click Go Live.

If you change your mind before saving, click Keep the demo domains for now.

Expected result: xCloud shows “Domain update request is sent for processing.” and moves every interface to its live domain. For a multi-domain app, all interfaces go live together; you cannot move just one.

Use Cloudflare for DNS and SSL

If your team has a Cloudflare integration, the Domain page shows Manage DNS & SSL with Cloudflare. Turn it on and xCloud checks each domain: domains found in your Cloudflare account show on Cloudflare, others show not found — use manual DNS. For domains not on Cloudflare, add the A records yourself as above. See using xCloud with Cloudflare for DNS management.

Set every domain at install time through the API

If you install a multi-domain One Click App through the xCloud Public API on a live domain, send the extra domains with the install request in additional_domains. Add one entry for each extra interface, with the domain in value and the interface in port. When you install on a live domain, the API requires a domain for every extra interface. On a demo (staging) install, you cannot send additional_domains: xCloud generates the demo domains, and you move to live domains later from the Domain page.

After the install, change a One Click App’s domains from its Domain page in the dashboard. The Public API’s domain update (PUT /sites/{uuid}/domains) refuses One Click template apps with a 422 error: “Domains of a one-click app are changed from its Domain page in the dashboard.” Other sites are not affected.

Change a live domain

  1. Open Domain → Domain on the live app.
  2. Edit the domain for the interface you want to change.
  3. Point the new domain’s A record at the server and click Verify My DNS.
  4. Click Save.

xCloud updates the app’s configuration with the new domains and keeps each interface mapped to the right container. Some apps store their main domain in settings outside xCloud (for example sign-in redirect URLs that other apps use). Update those settings yourself after a change.

HTTPS for the app is managed under Domain → SSL/HTTPS. See how to enable HTTPS in xCloud.

If the app has redirect domains, changing the main domain also changes where they send visitors: they now redirect to the new main domain.

Redirect extra domains to the app

A redirect domain sends visitors to the app’s main domain. Use it when people should reach the app from a second domain, for example an old domain or a short one. Anyone who opens a redirect domain gets a permanent (301) redirect to the main domain, and the rest of the address (path and query) is kept, so https://go.example.com/abc opens https://status.example.com/abc.

The app never sees the redirect domain: it keeps running on its own domain, so its links, sign-in and settings keep working. For an app with several web interfaces, redirect domains always go to the Primary interface.

Redirect domains are on the Domain page of a live app only. A demo site shows no Redirect Domains block, and the install form has none: move the app to a live domain first (see move a demo app to live domains), then add redirect domains.

Step 1: Add a redirect domain

  1. Open Domain → Domain on the live app.
  2. Under Redirect Domains, click Add Redirect Domain. An empty row appears.

Click ‘Add Redirect Domain’ under Redirect Domains on the Domain page of a live One Click App

Step 2: Enter the domain and point its DNS at the server

  1. Type the domain in the new row, for example go.example.com. Click Add Redirect Domain again for each extra domain.
  2. Point an A record for the domain to your server. The domain joins the list under Point an A record to your server.
  3. Click Verify My DNS. It checks the redirect domains together with the app’s own domains.

A redirect domain entered under Redirect Domains, with its A record listed under Point an A record to your server

To remove a redirect domain, click the remove button (×) at the end of its row, then save.

Step 3: Save

Click Save at the top of the Domain card.

Click ‘Save’ on the Domain card to apply the redirect domains

Expected result: xCloud updates the server’s web configuration and the app’s SSL certificate, which now covers the redirect domains too. A change to redirect domains alone does not restart the app. Open the redirect domain in a browser: it lands on the main domain.

If a domain can’t be used, xCloud shows the error under that row and saves nothing. Each redirect domain must:

  • be a valid domain name;
  • not be used by another site on the same server;
  • differ from the app’s main domain and from its interface domains;
  • point its A record at the server when xCloud issues the SSL certificate, or be in your Cloudflare account when you use Manage DNS & SSL with Cloudflare.

An app can have up to 20 redirect domains.

Find the app’s domains on the Credentials card

The app’s Credentials card (on the site overview, and under Access Data → Credentials) lists the main domain and every additional interface’s domain under the interface’s name. Use it to check which URL opens which part of the app.

Public TCP and UDP endpoints

Some apps serve a protocol that is not HTTP, for example a service clients connect to on a raw TCP or UDP port. When an app’s template declares a public TCP or UDP endpoint, xCloud:

  • assigns a host port for it on the server when the app is installed;
  • lists it on the Credentials card as Label (tcp) or Label (udp), with the address in the form SERVER_IP:PORT, for example 203.0.113.10:20001;
  • adds a note naming each port and protocol you need to open, for example “This app exposes port(s) 20001/tcp for external access.”

These ports do not go through NGINX, so they have no domain and no HTTPS. Clients connect to the server’s IP address and the listed port.

Credentials card of an xCloud One Click App listing a public TCP endpoint

Open the port in the firewall

The note on the Credentials card points you to the server’s Firewall Management page:

  1. Open the server and go to Security → Firewall Management.
  2. Add a rule for each port and protocol listed on the Credentials card.
  3. If only some clients should connect, limit the rule to their IP addresses instead of opening the port to everyone.

See how to configure Firewall Management in xCloud. If you add the rule on the server instead, xCloud suggests limiting the source, for example:

sudo ufw allow from YOUR_CLIENT_IP to any port 20001 proto tcp

Replace YOUR_CLIENT_IP and the port with your own values. Your cloud provider may also have its own firewall in front of the server; open the same port there if it does.

Do not rely on the server firewall alone to keep an endpoint private. Docker manages its own packet-filtering rules for published container ports, and those rules can take effect before UFW’s (see Docker’s packet filtering and firewalls documentation). After you set up the rule, test the port from a machine that should not have access. If it still connects, protect the service with the app’s own authentication or with your cloud provider’s firewall.

Connect a client

Use the address from the Credentials card in your client, including the port. If the client cannot connect:

  • check that the app’s containers are running on the site overview;
  • check the firewall rule for the exact port and protocol (a TCP rule does not open UDP);
  • check your provider’s firewall.

Keep a database private or open it to the internet

New One Click database installs are private by default. This section is about database apps you install from the One Click catalog, not Managed PostgreSQL, which is always private and has no public access option. A new database app, such as MySQL, PostgreSQL or Redis, only accepts connections from the server itself (127.0.0.1), not by server IP and port. If you need to connect from another machine, you can open it to the internet when you install it.

Apps that need open ports to work, such as game, voice or remote desktop servers, stay reachable as before and do not show this choice. Databases you installed before this option was added keep their current setting.

Step 1: Choose private or public on the install form

  1. Start the install as usual: Sites → New Site → One-Click Apps, then pick the database. See how to use One-Click App Templates.
  2. Below Site Details (and Domain Setup, if the app shows it), find Allow public access. It is off by default.
  3. Leave it unticked to keep the database private. Tick it only if clients outside the server must connect.
  4. Fill in the rest of the form and click Next.

Install form for a One Click database with the Allow public access checkbox, off by default

The checkbox shows only for databases and similar storage apps that don’t need open ports. The choice is made at install time; there is no switch to change it on an installed app.

Some apps can’t be installed privately. In that case the install shows “This template uses a shared network and cannot be installed with private port bindings.” If the install shows this message, the app can only run with Allow public access ticked.

Step 2: Connect to a private database

After the install, the app’s Credentials card shows Host 127.0.0.1 and the port xCloud assigned, with the note “Private access: connect from this server at 127.0.0.1 using the port shown below, or use an SSH tunnel. Apps in other containers need a separate private connection.”

Credentials card of a private One Click database showing host 127.0.0.1 and the Private access note

  • An app on the same server connects to 127.0.0.1 and the port on the card.
  • Your own computer (a database client such as TablePlus or DBeaver) connects through an SSH tunnel to the server, using 127.0.0.1 and the port on the card as the destination. Connect to PostgreSQL with an SSH tunnel shows how to set up a tunnel step by step.
  • An app installed as another One Click App runs in its own container, so it can’t reach the database at 127.0.0.1. xCloud does not connect two One Click Apps to each other. If you need this, contact our support team.

Step 3: Connect to a database with public access

If you ticked Allow public access, the Credentials card shows the server’s address and port (for example “Connect to 203.0.113.10:20002.”) and warns: “Public access is enabled. Docker-published ports can bypass the server firewall. Use an upstream firewall or Docker-aware filtering to restrict remote clients.”

Credentials card of a One Click database with public access, showing the server address, port and firewall warning

Keep the generated password. Block the port in your cloud provider’s firewall and allow only the IP addresses that need it. A rule in Firewall Management alone may not stop these connections (see the note under open the port in the firewall). Then test from a machine that should not have access: it must fail to connect.

Frequently asked questions

Can I point a second domain at my One Click App?

Yes, as a redirect domain. On the live app’s Domain page, click Add Redirect Domain, enter the domain and click Save. Visitors who open it are sent to the app’s main domain with a permanent (301) redirect, and the rest of the address is kept. The app itself keeps running on its own domain.

Why does my One Click App ask for more than one domain?

The app runs more than one web interface, such as a main app and an admin console. Each interface needs its own domain or subdomain, and all of them go live together.

Where do I find an app’s TCP or UDP address?

On the app’s Credentials card. Each public endpoint is listed by name and protocol with the server address and port, for example 203.0.113.10:20001.

Does xCloud open the firewall for a public endpoint?

No. The Credentials card tells you which ports and protocols to open and points you to the server’s Firewall Management page. Open each port there, then test from outside that only the clients you expect can connect.

Can anyone on the internet reach a new One Click database?

No. A new database app from the One Click catalog, such as MySQL, PostgreSQL or Redis, only accepts connections from the server itself (127.0.0.1), not by server IP and port. It is reachable from outside only if you tick Allow public access when you install.

If you run into any issues with your One Click App’s domains or endpoints, feel free to reach out to our support team.