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.