Please submit your support ticket via the interface in the customer area.įor most customers, this basic priority support has a response time of 3 working days, with a maximum of 1 support incident per month. Priority support for Enterprise customers If you are a Passenger Enterprise customer, then you are eligible for basic priority support. Security vulnerabilities email address Please report security vulnerabilities to We will do our best to respond to you as quickly as we can, so please do not disclose the vulnerability until then. Github issue tracker If you are experiencing a problem that you believe is a bug, please report it here. But support here is provided on a best-effort basis, so sometimes a bit of patience will help. Support on Stack Overflow is provided by the community, and our own developers also watch Stack Overflow on a regular basis. Stack Overflow Post a question on Stack Overflow if you are experiencing problems. We – Passenger's authors – are also ready to help you whenever we can. Passenger has a friendly community of users who look out for each other. If you are stuck with a problem, please do not hesitate to contact one of the support resources. 5 Out of ideas? Try the support resources Try learning more about the activities that Passenger perform it may help you with understanding the problem and with troubleshooting. If you don't know what Passenger does, then problems may seem opaque. Passenger takes care of a lot of things for you under the hood. If upgrading Passenger didn't help, and you don't think your problem is caused by a bug, then please continue with this troubleshooting guide. If you suspect that your problem is a bug in Passenger, and upgrading didn't fix it, please report the bug to our Github issue tracker.
#Bitnami mean stack for ruby on rails upgrade
Please upgrade Passenger to the latest version and check whether the problem is still there. Passenger is under active maintenance and development, so there is a chance that – assuming you really ran into a bug – the bug is already fixed. Some problems are caused by bugs in Passenger.
3 Upgrade Passenger to the latest version So if you're using Rails, please be sure to check production.log instead of development.log. Note that Passenger runs applications in the "production" environment by default (that is, Passenger sets RAILS_ENV, RACK_ENV, NODE_ENV and related environment variables "production"). Note that this file does not contain errors that Rails encounters during startup – those kinds of errors are typically written to STDERR, which means they end up in the Passenger log instead. When an error occurs during request handling, it is typically logged here. You should also check that file to see whether your application or web framework has logged any important messages.įor example, Ruby on Rails logs to log/development.log and log/production.log. The application or web framework may have its own log file that is independent from the Passenger log file. Not finding anything useful in the Passenger error log? Please read Troubleshooting logging problems. Or, if you configured the PassengerLogFile directive, then the log file is in the referenced file. You can find out the exact location of the error log by running passenger-config -detect-apache2. This is typically located in /var/log/apache2/error_log. The Passenger log file is the global (not the per-vhost) Apache error log file. This typically consists of errors that the application encounters during startup, but not errors that it encounters when it's handling requests. Everything that the application writes to STDOUT and STDERR.Passenger info, warning and error messages.The log file is where Passenger prints to when it encounters a problem or when it wants to tell you something. One of the first things you should do upon encountering a problem, is to check the Passenger log file. This page provides guidence on what to do when you encounter problems.įirst things to try 1 Check the Passenger log file Edit page Troubleshooting Passenger + Apache and Ruby
0 kommentar(er)
