Edit page

Upgrading Passenger + Apache

How to upgrade Passenger + Apache depends on how Passenger was installed. Please select the option most relevant to you.

Table of contents

  • Loading...

macOS (Homebrew)

If Passenger was installed on macOS through Homebrew, then you can upgrade Passenger as follows:

brew update
brew upgrade passenger

When done, read the Homebrew formula caveats and follow any Apache-specific instructions you see:

brew info passenger

Debian packages (Debian, Ubuntu)

If Passenger was installed through the Phusion Passenger APT repository, then you can upgrade Passenger along with Apache through APT using the following command:

sudo apt-get update
sudo apt-get upgrade

Don't see any updates?

If you don't see any updates, then there are two possible reasons:

  1. Our Debian packages haven't been released yet. When we release a new version of Passenger, it typically takes 1-2 hours for our server to build Debian packages.
  2. If you are using a non-Long Term Support version of Ubuntu, then it is possible that we have dropped support for that Ubuntu version.

RPM packages (Red Hat, CentOS)

If Passenger was installed through the Phusion Passenger YUM repository, then you can upgrade Passenger along with Apache through YUM using the following command:

sudo yum update

Don't see any updates?

If you don't see any updates, then maybe our RPM packages haven't been released yet. When we release a new version of Passenger, it typically takes 2-3 hours for our server to build RPM packages.

Heroku

If you are using Passenger on Heroku, then update the passenger gem by running:

bundle update passenger

Then commit and push to Heroku:

git commit -a -m "Upgrade Passenger to latest version"
git push heroku master

Docker

Please refer to the passenger-docker website for upgrade instructions.

Source tarball

If Passenger was installed through a source tarball, then please follow the source tarball upgrade guide.

RubyGems

If Passenger was installed through RubyGems, then upgrading Passenger involves going through the normal installation process again. Please follow the installation guide that is most relevant to you:

Please ignore the warning there that tells you that the guide is not for updates.

When done, please don't forget to update the Apache configuration snippet that the installer tells you about at the end.