TomasP
TomasP10mo ago

Customizing unexpected error pages

When having a multi-instance Zitadel setup with top subdomain as the tenant (instance). We get an error page with an instance not found error, when a user hits a non-existing instance. This page is blank, is it possible to configure to make it more professional looking? This could also be applied to other unexpected errors displayed. Right now we get text i.e.:
unable to set instance using origin &{non-existant.127.0.0.1.sslip.io http} (ExternalDomain is zitadel.127.0.0.1.sslip.io): ID=QUERY-1kIjX Message=Instance not found. Make sure you got the domain right. Check out https://zitadel.com/docs/apis/introduction#domains
unable to set instance using origin &{non-existant.127.0.0.1.sslip.io http} (ExternalDomain is zitadel.127.0.0.1.sslip.io): ID=QUERY-1kIjX Message=Instance not found. Make sure you got the domain right. Check out https://zitadel.com/docs/apis/introduction#domains
8 Replies
TomasP
TomasPOP10mo ago
Hey, any insights on this issue?
FFO
FFO10mo ago
I guess you are self-hosting, right? In that case you can configure your reverse proxy to render an error page or redirect to another domain.
TomasP
TomasPOP10mo ago
Yes, we are self hosting, it's just that all our tenants are "dynamic" and we don't have a list beforehand... Should this be solved by some sort of k8s ingress configuration?
FFO
FFO10mo ago
Ok I see, in that case you either want to dynamically check the domain and react in the network infra or we can have something in zitadel that creates a nice error. What would you think is the best open in your case?
TomasP
TomasPOP10mo ago
I have a feeling that a network infra solution would be very custom and only tailored at our specific case. Zitadel would be better of providing some sort of simple theming for this unexpected error (like it has with access denied, login and other pages). This should be a generic page, the only difference could be to choose the error message and details to display on that page... Just some thoughts.
FFO
FFO10mo ago
Thanks for sharing, let me loop in @fabienne as well here
fabienne
fabienne10mo ago
Thanks for the feedback. Till now we never heard the need for such an error page in that case. I think mainly because most of the time this error indicates that there has been a configuration problem somewhere. If this is something you like to see in Zitadel. I kindly ask you to open up a feature request in our repository. In that case we can track how many customers would love to see that feature.
TomasP
TomasPOP10mo ago
We are going to use default k8s fallback service with a custom error page for now, but i'll fill a feature request on github, as you mentioned, to check if there's a need for a customizable unexpected error page directly in Zitadel...

Did you find this page helpful?