Overview Running the Engine Yard Core API Ruby client and CLI utility (ey-core) on Windows when deploying via the CLI or executing other operations through the CLI can sometimes throw the following er...
Overview If you are having issues with an instance in your environment and the cause of the issue is not apparent in the UI, you will need to access the instance to review the available logs and the a...
Monitoring your application is always a good idea when deploying it into production. Engine Yard Cloud automatically monitors your environment and adds alerts to the dashboard when abnormal resource u...
Engine Yard stacks stable-v1 and stable-v2 were EOLed several years ago and are no longer actively maintained. Their outdated software versions, and in particular their lack of support for TLS v1.2 ca...
Overview Here are some things to check when troubleshooting your deployment because it failed or is not working as expected. Topics on this page: View the deployment log file 500 errors after deployin...
Engine Yard utilizes Phusion Passenger Standalone in conjunction with nginx on Stack V5 (16.06) of the platform. Customers have the option to choose between Passenger5, Puma and Unicorn but this artic...
This document describes some common error conditions you might see while setting up your Engine Yard Cloud environment. Common error conditions 1. Gem Not Found Error While deploying an application, y...
The Engine Yard platform defaults to Bundler version 1.0.10, which throws the above error with newer versions of Rubygems. A common fix for this is to specify the Bundler version. If the version of Bu...
Overview You may be experiencing issues in your environment after individually terminating one of the instances within the environment. This article explains why these issues arise and how they can be...
Overview You are trying to SSH into one of your instances but are unable to. You may receive any of the following error messages: Invalid public key Permission denied (publickey) Solution To be able...