Web Interface on Domain B fails to connect to Adaxes Service on Domain A

Question

Hi everyone,

I am deploying a new Adaxes Web Interface instance in a cross-domain environment and running into a connection/discovery issue.

My Scenario:

Domain A: Contains the main Adaxes Service (Backend) and the Configuration Set.

Domain B: Contains the IIS Web Server where I am installing the Web Interface.

The Problem:

During the web interface setup, I am installing the package via command line, specifying only the Configuration Set ID like this:

msiexec /quiet /i "adaxes.msi" ADDLOCAL=AppWebUIFeature ADMWEBSERVICECONFIGSET="<configSetId>"

However, looking at the Web Interface trace logs right after installation, the application constantly attempts to perform a Service Discovery (SCP query) on the local domain where the IIS machine is joined (Domain B), completely ignoring the remote domain. This results in the following loop:

The following Adaxes services found on DomainB: None

SelectNearestServiceException: Adaxes service connection failed.

Question:

Since I am performing a standard installation just by providing the Configuration Set ID, how can I force the Web Interface installer or the application to explicitly look for the Configuration Set on Domain A instead of defaulting to the local Domain B's SCP? Is there a specific installer property or an official way to handle this cross-domain discovery block?

Thanks in advance for your help!

Comments

Hello,

Do we understand correctly that you installed the web interface component in domain B successfully, but it does not connect to Adaxes service in domain A?

If that is correct, to help us troubleshoot the issue, please, provide a screenshot of the Multi-server environment dialog. The dialog displays how many Adaxes services you have and what their versions are. For information on how to view it, see https://www.adaxes.com/help/MultiServerEnvironment. You can post the screenshot here or send to us at support@adaxes.com.

---

Hello Support team,

Yes, your understanding is correct about the connection failure. However, to clarify the environment layout: the backend and frontend components are deployed on completely separate virtual machines residing in two different domains.

The Adaxes Service (Backend): We have a single backend service instance running inside Domain A.

The Web Interface (Frontend): We have two separate IIS Web Servers running inside Domain B (where I am experiencing this issue).

Because the Web Interface VM is joined to Domain B, it cannot find any Adaxes Service locally. It needs to look across the domain boundary to reach the single backend in Domain A, but the logs show it keeps querying the local Domain B via SCP.

As requested, here is the screenshot of the Multi-server environment dialog taken from our configuration. As you can see, the environment is healthy and contains a single backend instance.

Given this cross-domain dual-VM setup, how can we force the Web Interface instances in Domain B to bypass the local domain SCP query and target Domain A's backend?

Thank you!

Answer 1

Hello,

Thank you for the provided details. The issue can occur in such a setup in case domain B is not managed in Adaxes. To remedy the issue, try to do the following on the computer in domain B where the web interface component is installed:

1. Navigate to the folder where the web interface is installed. By default, the folder is C:\Program Files\Softerra\Adaxes 3\Web Interface\App.
2. Open the appsettings.xml file with a text editor.
3. Locate the configuration\adaxes.web.ui XML element.
4. Set the lookupServiceDomainName attribute to domain A.

   <adaxes.web.ui adaxesConfigurationSetId="{93294e43-4d1e-41bd-984b-cba6b570a748}" lookupServiceDomainName="domainA.com">
    <trace enabled="false" filePath="${basedir}/adaxes.webui.trace.txt"/>
   </adaxes.web.ui>

5. Save the file.
6. Check whether the issue persists.

Comments

Hi, Thank you for your help!

I applied the lookupServiceDomainName attribute as suggested and it worked correctly. The Web Interface in Domain B is now connecting to the Adaxes Service in Domain A without issues.

Thanks again for the quick support! Best regards, Leonardo