Does 2025.1 support different roots or multiple hostnames (on a single server)?

Question

We have a need to expose a single subsite from one of our Adaxes installations through Windows's WAP.

With 2023.1 and 2023.2, I was able to add /Adaxes/api, /Adaxes/ClientApp, and /Adaxes/specificSubSite to the WAP and it functioned without issue. However, the update to 2025.1 and the web interface changes moved all of the CSS and JS to the root /Adaxes directory and we do not want to expose all of Adaxes.

Is it possible to configure a second website in IIS to expose just the minimum needed to get this subsite to function? Something like /Adaxes is only the subsite we want with no other Adaxes functionality enabled.

Answer 1

Hello,

For details on how to expose Adaxes web interface to the Internet, have a look at the corresponding section of the installation guide: https://www.adaxes.com/help/InstallationGuide/#exposing-web-interface-to-the-internet. On the server where the web interface will be installed, you can allow only a specific one for access. To configure that, use the Web servers functionality in the Access Control section of the web interface configurator.

Comments

It is actually just internal, not to the Internet. Hmm, we could maybe do that if we setup a secondary installation of Adaxes. Is it possible to create a second website (like /Adaxes2 instead of /Adaxes with its own configuration, etc.) on the same server instead of installing Adaxes on another server?

---

Hello,

Unfortunately, there is no such possibility. If installing Adaxes web interface on another computer is not an option, you can try creating a separate web site in IIS and redirect it to the required web interface.

---

I did try creating a second website, copied the Web Interface folder, and recreated the IIS applications pointing to the new copy of the folder, but used the same App Pool identities as the existing ones.

This did not really work. I was able to get into the new site, but I could not also access the other site (ASP.NET Core error about more than one application in an app pool not supported) at the same time. And, any changes I made within the "new" Config portal were reflected in the "old" website.

If I use different App Pool identities, would that make a difference? Is the site configuration information stored in the database based on the app pool identity or something else? Is there a way to tell the Adaxes service the new application is using a different hostname?

---

Hello,

If I use different App Pool identities, would that make a difference?

This is not an Adaxes related question, but according to the IIS errors it should work fine.

Is the site configuration information stored in the database based on the app pool identity or something else?

Unfortunately, that is not something we can assist you with as the question is not related to Adaxes in any way. We recommend you to check with Microsoft support for all the required details.

Is there a way to tell the Adaxes service the new application is using a different hostname?

There is nothing like that. You can only specify the corresponding data during web interface installation and nothing else. As we mentioned in the previous post, you can just redirect the new IIS web sire to the required web interface. There is no possibility to have Adaxes applications on the same computer in multiple IIS sites.