-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Closed
Labels
Description
Describe the bug
My rails server in production is rejecting connections for reasons I do not understand. When I try to connect via browser I receive the following error message from Chromium:
This site can’t be reached. cinemeeting.eu refused to connect. ERR_CONNECTION_REFUSED.
Puma config:
I copied and pasted config/puma.rb from Heroku documentation, although I have deployed my application to NetCup, a German hosting provider, via dokku, following instructions in the Dokku documentation:
workers Integer(ENV['WEB_CONCURRENCY'] || 2)
threads_count = Integer(ENV['RAILS_MAX_THREADS'] || 5)
threads threads_count, threads_count
preload_app!
rackup DefaultRackup
port ENV['PORT'] || 3000
environment ENV['RACK_ENV'] || 'development'
on_worker_boot do
# Worker specific setup for Rails 4.1+
# See: https://devcenter.heroku.com/articles/
# deploying-rails-applications-with-the-puma-web-server#on-worker-boot
ActiveRecord::Base.establish_connection
end
The only help I received so far is from josegonzalez at GitHub who suggested my application should listen to all interfaces and respect the PORT environment variable. How can I make puma listening to all interfaces with the bind statement? Is it necessary?