If you accidentally configure the filter chain wrongly in Magnolia you can easily break the complete instance and prevent it from starting up again.

E.g. consider the following scenario:
1. Start (an already installed) Magnolia instance
2. add a bypass configuration on the Main Magnolia Filter (/server/filters) node
3. add property class=info.magnolia.voting.voters.URIStartsWithVoter
now, when adding the property "pattern" you'll get a 500 when hitting enter due to a Null exception. This happens since Content2Bean is not able to initialize the filter chain again.

See the exception attached.