While dealing with some issues with mod_passenger over the last few days, we’ve observed that quite a number of people are enabling mod_passenger on their domains and not actually using it for anything. Because of this we’ve made a restriction for mod_passenger where the path to the web directory must actually have /public at the end, to (hopefully) prevent people from enabling it without any need to do so.

To take care of the existing domains which have been set up in this fashion, we disabled mod_passenger on any currently hosted domain which wasn’t pointing at a /public directory. There are a few of you who might have a symlink to a rails application’s /public directory, you simply need to re-enable mod_passenger through the web panel to get it working again.

If you have any questions, please feel free to contact support, and we can assist you!