502 page when metabase is stopped
Summary
When metabase is stopped, during data update every night, we encounter a 502 error code
Steps to reproduce
- Start nginx
docker-compose up -d nginx
(this starts dependent services) - Stop metabase
docker-compose stop metabase
- Go to localhost/metabase
What is the current bug behavior?
The page hangs, then shows a 502 page. On eurosfordocs.fr, we get the same error, with a 502 page by cloudflare.
What is the expected correct behavior?
We would like to redirect to a default jekyll page, explaining that metabase is under maintenance and will be available again soon
Possible fixes
- Add a 502.md page on jekyll
- Modify nginx.conf to redirect to this page when getting 502 on host/metabase