Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

On a shared server (specifically a DreamHost shared server running Debian, but I don't know if this matters) with mod_suexec activated and with PHP and Python forced to use CGI or FastCGI, would you expect Passenger processes to be run as the Apache user or as the user from whose home directory the Passenger-powered app is run?

Please explain the basis for your answer.

(I'm guessing the latter, for consistency with DreamHost's approach to PHP and Python, but I'm vague on how Passenger interacts with Apache, let alone with mod_suexec.)

share|improve this question
up vote 2 down vote accepted

mod_suexec is specific to CGI setups, which a completely different technology from passenger.

Passenger implements its own way of user switching. The user applications are run as is determined broadly according to the following:

  1. If we are a Rails app, run as the owner of config/environment.rb. If we are a Rack app, run as the owner of
  2. If the determined user would be root, use the configured PassengerDefaultUser
  3. If this still would be root (or unconfigured), run as the user, Apache runs at (e.g. wwwrun or www-data).

For more information, see

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.