Ethora Community

Community › Developers (platform specific questions) › Backend, API, Admin Dashboard

Setting up DNS and services endpoints for your dedicated Ethora server

Archived from the Ethora community forum. First posted on 18 December 2025; product details may have changed since. For current setup see Get Ethora and GitHub.

All you need to do is set up DNS records for subdomains to point to your IP address.

The routing will be taken care of automatically by Ethora server (assuming a standard "monoserver" setup).

This can be achieved using your domain name DNS management system, for example Cloudflare or Route53.

The A records you need to set up are:

  • app

  • api

  • xmpp

  • files

Description:

  • app. - frontend application for admin panel of your Ethora platform instance. Alternatives: admin., ethora., dashboard. etc

  • api - API endpoint for your Ethora API. Alternatives: ethora-api, chat-api etc.

  • xmpp - XMPP messaging server endpoint for chat server XMPP websocket connections. Alternatives: chat, messaging etc.

  • files - endpoint for Minio services (used for files attachments etc)

These subdomain names can be modified if you prefer. In such case these modifications should be reflected in your installation deploy.yml configuration.

Cloudflare:

CleanShot 2025-12-18 at 11.50.16@2x.png

As result you should have A-records for all Ethora services pointing to your IP address, for example:

CleanShot 2025-12-18 at 11.54.47@2x.png

You can verify whether subdomains resolve to your IP address using 'host' command from your terminal:

CleanShot 2025-12-18 at 12.18.09@2x.png

In case of a service-only domain name (when it's only used for your Ethora server purposes), the full DNS configuration will look similar to this (replace with your own IP and domain name):

CleanShot 2025-12-18 at 12.05.38@2x.png

Have a question about this? Ask the Ethora team.