I have installed the package Maintenance Mode V8 2.0 by Kevin Jump in my Umbraco 8.6 installation. I like how it works and it works just fine as expected during debugging in Visual Studio 2019 on my local server. Once I published the site to my hosting provider ASPHostPortal, it stops working and displays the message " service is unavailable". If Maintenance Mode is off it works just fine. I'm wondering is there something in IIS that needs to be turned on or an extension that needs to be installed to allow the redirect to the Maintenance page. Or is there a ASP.net web config setting that I need to add to ensure that this works. Thanks for any help in advance!!
Experiencing the same issue on an IIS, works great on local machine and also if I go to the server and call the website locally there, but not from any remote machine.
Did any of you solve this? Looks like it´s some customError handling that returns the page for 503.
Maintenance Manager : service is not available
I have installed the package Maintenance Mode V8 2.0 by Kevin Jump in my Umbraco 8.6 installation. I like how it works and it works just fine as expected during debugging in Visual Studio 2019 on my local server. Once I published the site to my hosting provider ASPHostPortal, it stops working and displays the message " service is unavailable". If Maintenance Mode is off it works just fine. I'm wondering is there something in IIS that needs to be turned on or an extension that needs to be installed to allow the redirect to the Maintenance page. Or is there a ASP.net web config setting that I need to add to ensure that this works. Thanks for any help in advance!!
Hi!
Experiencing the same. Working correctly on localhost but displays "The service is unavailable." when trying on Azure.
Have you had any luck solving this?
Thanks, Istvan
Experiencing the same issue on an IIS, works great on local machine and also if I go to the server and call the website locally there, but not from any remote machine.
Did any of you solve this? Looks like it´s some customError handling that returns the page for 503.
yes, you need to set up error handling in your web.config like below
and
Thanks, that´s the same solution I came up with,
But this circumvents the possibility in the package to choose your own MaintenancePage in Umbraco, if it´s already fixed here.
you would obviously need to update the web.config to match the template used, we use a custom one called UnderMaintenance
is working on a reply...