Whenever your application is stopped, you are presented with the infamous green monsters. To present your app users with a more professional looking page when the application is down, Mendix enables the creation of custom error pages on Mendix Cloud.
You can create an
offline.html page, a
404.html page, and a
The different files serve different purposes:
offline.html: will be served when your application has been stopped manually
404.html: will be served whenever a path does not exist
403.html: will be served when access to a resource is denied, because an IP filter has been implemented or because of client certificate restrictions.
If you do not create these files, the default “green monsters” will be used instead for each scenario.
This how-to will teach you how to do the following:
- Create a custom error page
Before starting this how-to, make sure you have completed the following prerequisites:
- Have a local repository of the app
- Have your app hosted in the Mendix Cloud
3 Create a Custom Error Page
Open the local folder of your app.
Go to theme.
Create a new folder named error_page.
In the error_page folder, place your offline.html file.
Optionally, you can also create 404.html and 403.html pages.In these .html files, you can only refer to external resources or resources under the absolute path
/error_page/path is the only one that will be available when the application is stopped.
Commit the changes in the Desktop Modeler.
It might take up to an hour to before the custom error page is visible when the app is offline.
3.1 Example Offline Page
offline.html/404.html/403.html page could look like this:
<!doctype html> <html> <head> <link rel="stylesheet" type="text/css" href="/error_page/style.css"> <script src="/error_page/script.js"></script> </head> <body> This application is currently offline. </body> </html>