dreamhost

Greetings, Does anyone know what are the required fields to have Django send emails when a "500 Internal Server Error" happend? I am hosting my project on Dreamhost and for the life of me I can't get Django to send emails. What are the required fields when hosting on Dreamhost? As proposed by S.Mark, you can use gmail. Here is what you need in your settings.py ADMINS = ( ('Your Name', 'your_name@email.com'), ) EMAIL_HOST = 'smtp.gmail.com' EMAIL_PORT = 587 EMAIL_HOST_PASSWORD = 'password' EMAIL_HOST_USER = 'gmail_account' EMAIL_SUBJECT_PREFIX = 'something' EMAIL_USE_TLS = True Yes, I am, same

My website has been broken since Dreamhost upgraded their servers a couple of weeks ago. I have been tearing my hair out trying to get it fixed and made some progress but am stuck on what is hopefully the final issue. I'm using Rails 3.1.1 on Ruby 1.8.7 and get presented with a 'Ruby (Rack) application could not be started error' from PhusionPassenger. It states that it 'Could not find a JavaScript runtime. See https://github.com/sstephenson/execjs for a list of available runtimes. (ExecJS::RuntimeUnavailable)'. Searching for this on Dreamhost's wiki has suggested a solution to install

On DreamHost shared hosting, I'm setting up htpasswd, but Apache does not have permission to read the file. How do I give it permission? I want to either change the owner or group of the .htpasswd file instead of giving it insecure permissions. I don't think I have access to the httpd.conf file, so I can't use this method to find what user Apache runs as . Also, running top or ps aux only shows the processes I'm running but doesn't show the apache process. Based on the output from cat /etc/passwd and cat /etc/group , I'm guessing it's www-data . Well, I followed the instructions for Password

i am getting the following error Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, webmaster@strivemedicare.in and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request. We use DreamHost and the link to the URL is http:/

My Laravel 5 has run OK until the database was configured, then found this error: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name or service not known Doing some research it seems that I configured MySQL access too late, so I should restart the server in order to get the correct environment variables. Well, I'm using Dreamhost's shared server and I just can't do that. How should I fix this issue? Thanks If you have run php artisan config:cache on your server, then your Laravel app could cache outdated config settings that you've put in the .env file. Run php artisan

I'm trying to run a Ruby on Rails app on a Dreamhost shared server. All is well so far except one weird bug I have not been able to unravel. Sometimes when I visit the web app, I get presented with a Phusion Passenger error saying, You have already activated rack 1.2.1, but your Gemfile requires rack 1.2.2. Consider using bundle exec. When I just refresh the page it seems to work, though - no more Phusion Passenger error message. Following other stack overflow threads and a similar Dreamhost wiki , I added the following to the top of the config/environment.rb file: if ENV['RAILS_ENV'] ==

I am hosting a Ruby on Rails 2.0.2 application on DreamHost. It is on an Apache 2 server, running on top of Phusion Passenger. The application often returns a 500 error "Rails application failed to start properly", but at random times. It appears to happen when the application is under higher load, though I can't confirm this. It only gets about 2,000 pageviews per day, so I don't think load should really be an issue. The Apache logs correlate these 500 responses with the error: "Premature end of script headers". Just looking at the logs at 9 AM today, the error appears as often as three or