Strange problems encountered after becoming a multi instance in Azure

Northern Lights asked on July 7, 2025 05:37

We are using the. net MVC version of Kentico13. We deployed our admin site and web site on Azure using the same primary domain name(example.com and example.com/admin). Due to the increasing number of customer visits, we have increased the default instance count(1 to 2). But when we did this, we found that our database memory usage increased(55% to 75%), and occasionally one of the two instances would not be able to access the database(also store in Azure). Occasionally, administrators can log in and manage the landing page normally, but cannot upload new media files

We have decided to follow your suggestion and deploy our admin site separately. But we encountered some problems. Because the domain name of my testing environment is stage.exeample.com. How can we keep our staging and prod consistent. Can we use stagengadmin.example.com, or do we have to use admin.staging.exemplar.com. At the same time, you mentioned earlier that the license for admin.xample.com is free. We need to perform additional operations to obtain this license and add it to the license key on the kentico admin page. Or we don't need create a new license for our website.

Correct Answer

Juraj Ondrus answered on July 7, 2025 06:26

Are you hosting the admin app under the same WebApp instance on Azure, are you nesting the admin app? If yes, this is not supported and the admin app should be running on its own AppService.
Also, Are you using automatic web farms and shared file system as described in the Azure scaling documentation?
Are there any errors in the Event log?
What is the database tier? Is it capable of handling the load? You may want to scale the DB as well.

1 votesVote for this answer Unmark Correct answer

Recent Answers


Northern Lights answered on July 7, 2025 08:31 (last edited on July 7, 2025 08:34)

So, is it true that Kentico requires us to create a single Azure app service to host our admin system for multi-instance web service. We are using SQL Server. So far, we don't want to expand the database as well, considering that it didn't have that much pressure originally. What seems to be the problem causing the increase in memory usage of the database. And our web form mode is Automatic.

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on July 7, 2025 09:29

Well, if you add more instances which are generating SQL queries to the DB, then some increase is expected.

1 votesVote for this answer Mark as a Correct answer

Northern Lights answered on July 8, 2025 05:36

Thank you for your answer, it is very helpful for us. But this also brings a new problem, if we deploy admin site to a separate App service using different domains. Do we need to pay for an additional Kentico license

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on July 8, 2025 05:45

No, the admin domain for one instance is already covered. See the licensing documentation. One admin domain is already covered.

1 votesVote for this answer Mark as a Correct answer

Northern Lights answered on July 16, 2025 05:06

We have decided to follow your suggestion and deploy our admin site separately. But we encountered some problems. Because the domain name of my testing environment is stage.exeample.com. How can we keep our staging and prod consistent. Can we use stagengadmin.example.com, or do we have to use admin.staging.exemplar.com. At the same time, you mentioned earlier that the license for admin.xample.com is free. We need to perform additional operations to obtain this license and add it to the license key on the kentico admin page. Or we don't need create a new license for our website.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.