# Custom Error Backend for default nginx-ingress

**URL:** <https://forums.suse.com/t/custom-error-backend-for-default-nginx-ingress/11646>\
**Category:** SUSE Rancher Prime\
**Created:** [August 30, 2018, 1:39pm UTC](https://forums.suse.com/t/custom-error-backend-for-default-nginx-ingress/11646 "2018-08-30T13:39:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stonedge](https://avatars.discourse-cdn.com/v4/letter/s/d07c76/32.png) [@Stonedge](https://forums.suse.com/u/Stonedge)\
**Post date:** [August 30, 2018, 1:39pm UTC](https://forums.suse.com/t/custom-error-backend-for-default-nginx-ingress/11646/1 "2018-08-30T13:39:34Z")

</div>

How could I overwrite the default system image used as ingress default backend in rancher 2.0.x?

Long Story Short: I want to replace the “default backend - 404” error page… Since Rancher 2.0.x used the ingress default backend 1.4 image… it’s impossible to inject a custom error page inside that image, instead I would like to use the default ingress custom error image( [quay.io/kubernetes-ingress-controller/custom-error-pages-amd64:0.3](http://quay.io/kubernetes-ingress-controller/custom-error-pages-amd64:0.3) ) which would enable me to mount a configmap to fill the /www folder inside that container…

I don’t really like the Idea of disable the default ingress to deploy a custom one just for that need… it’s sound a little overkill at my point of view just for changing the error page…

With rke modifying system\_images directive (ingress\_backend) would do the job but how should I process in rancher 2.0 to remain compatible with cluster upgrade?

Did using the custom error image by default as been considered by the rancher team? (just asking…)

Thanks in advance

---

<div class="post-metadata">

**Author:** ![zchef2k](https://avatars.discourse-cdn.com/v4/letter/z/4af34b/32.png) [@zchef2k](https://forums.suse.com/u/zchef2k)\
**Post date:** [October 22, 2018, 2:50pm UTC](https://forums.suse.com/t/custom-error-backend-for-default-nginx-ingress/11646/2 "2018-10-22T14:50:27Z")

</div>

+1

Being able to provide custom error responses with the default controller is almost a must.

---

<div class="post-metadata">

**Author:** ![ChartsWatcher](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/chartswatcher/32/7109_2.png) [@ChartsWatcher](https://forums.suse.com/u/ChartsWatcher)\
**Post date:** [January 16, 2021, 10:24am UTC](https://forums.suse.com/t/custom-error-backend-for-default-nginx-ingress/11646/3 "2021-01-16T10:24:50Z")

</div>

Has anyone found a solution for deploying custom default backend when using rke?