[Bug]: Unable to Set Up Domain and SSL Certificate on Azure ACI Because the Assigned IP Changes

[ame-appsmith]

Is there an existing issue for this?

• I have searched the existing issues

Description

The user installed Appsmith on Azure ACI using our guide. They have set up a subdomain and an SSL certificate for the ACI. The problem in Azure ACI is that the assigned IP changes. This means that every time the IP changes they have to adjust the DNS settings for the subdomain. For this reason, the installation option via Azure ACI when using their own subdomain with an SSL certificate doesn't work.
There is a tutorial that describes how to assign a fixed IP to the ACI using Caddy, but even with Caddy, they'll have to update the DNS record to get HTTPS:

[...] you just need a public DNS record and Caddy needs to be reachable via ports 80 and 443.

So that DNS record with the correct IP address will still be needed.

Steps To Reproduce

Set up a subdomain and an SSL certificate for the ACI. Because the assigned IP changes, you have to adjust the DNS settings for the subdomain.

Public Sample App

No response

Environment

Production

Issue video log

No response

Version

Self-Hosted

[sharat87]

Unfortunately, this can't be solved with the things that Appsmith has control on. With or without HTTPS, for a domain to point to the Appsmith running on a server, the domain has to have an A-record with the IP of the server. But, if the ACI can work with a load balancer that can abstract the changing IP address, then we can perhaps configured the domain to have a CNAME-record (instead of the A-record), and let the load balancer deal with the changing IP address. I'm not very familiar with Azure terminology to give details here, but being unable to configure a domain because of a changing server IP, is not something solvable from within Appsmith.

Let me know if I'm misunderstanding this issue and we can reopen. Closing.