If you run into this problem, which by the way usually happens after upgrading the rubygems package (in my case it was to version 1.8.21
), your best bet is to upgrade the gem from the backtrace of this error. In my case it was the old passenger version 3.0.9
, which was causing this problem. Upgrading to 3.0.11
solved it.