I'd like to modify the generic blank page with a custom template

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

2 Answers 2


Create/edit the errors/local.xml file like this:

<?xml version="1.0"?>

Then create a copy of errors/default folder and call it customtheme.

From this point, you can edit the phtml files as well as add the css files to create your own custom theme.

EDIT: even though it has been approved as a valid answer, this answer is only relevant for Magento 1 and I did not see it was a Magento 2 question.

Thus, the right way of designing the maintenance page is by editing the pub/errors/default/503.phtml page.

  • Is it the local.xml under <m2root>/pub/errors?
    – csmarvz
    Jan 13, 2016 at 10:09
  • If your Magento install is under /pub I guess so. Find out where your app folder is, the errors folder should be on the same level. Jan 13, 2016 at 10:10
  • Inside my Magento install are: app, bin, dev, lib, phpserver, pub, setup, update, var, vendor. Inside app are: code, design, etc, i18n. But no errors folder :/
    – csmarvz
    Jan 13, 2016 at 13:39
  • Interesting, and how does your 503 page looks like right now ? Does it look like the Magento default theme or totally white ? Jan 13, 2016 at 13:42
  • It looks totally white
    – csmarvz
    Jan 13, 2016 at 14:15

Actually, you don't need to edit core files for this purpose. Just copy pub/errors/local.xml.sample to pub/errors/local.xml, then make a copy of pub/errors/default (let's say pub/errors/custom). Change the skin value of the pub/errors/local.xml to the newly created errors skin:


After this you are able to make changes in pub/errors/custom/503.phtml and other files.

  • Yup, this one is the correct answer for M2. Dec 12, 2016 at 7:26
  • 2
    Great idea, but this is broken in the 2.1.* branch. There's a fix that should be released in 2.2 So if you are using 2.1 then... sorry, no custom skin for you - see github.com/magento/magento2/issues/4305 Apr 13, 2017 at 12:06
  • 1
    I can confirm @yaroslav-rogoza solution is working in 2.1.4 Enterprise.
    – diazwatson
    May 25, 2017 at 1:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.