代码之家 › 专栏 › 技术社区 › Poilon

在Heroku上使用ActionCable部署Rails5 beta3应用程序时,Redis密码无效

actioncable ruby-on-rails-5 heroku ruby ruby-on-rails

Poilon · 技术社区 · 9 年前

首先,我的应用程序在开发中运行良好。我一直在按照教程在Heroku上部署Action Cable应用程序,但我遇到了这个问题:

我的应用程序的配置是这样的:

配置/电缆.yml:

development: &development
  :url: redis://localhost:6379
  :host: localhost
  :port: 6379
  :timeout: 1
  :inline: true
test: *development
production: &production
  :url: redis://redistogo:MYREDISTOGOPASSWORD@lab.redistogo.com:10108/
  :host: tarpon.redistogo.com
  :port: 10108
  :password: MYREDISTOGOPASSWORD
  :inline: true
  :timeout: 1

初始化器/redis.rb

uri = URI.parse(ENV['REDISTOGO_URL'] || 'redis://localhost:6379/' )
REDIS = Redis.new(host: uri.host, port: uri.port, password: uri.password)

config/routes.rb中的这一行

mount ActionCable.server => '/cable'

在生产中的应用程序中,我没有JS控制台错误或警告,但在日志中,我可以看到为什么ActionCable魔法不起作用,当websocket尝试访问它时,我的redistogo密码似乎是错误的?
我可以 heroku run console 然后尝试 REDIS.set()/get() 而且效果很好。

在日志中,我遇到了以下错误:

2016-04-23T23:26:36.308976+00:00 app[web.1]: [3] - Worker 0 (pid: 1078) booted, phase: 0
2016-04-23T23:26:36.316316+00:00 heroku[router]: at=info method=GET path="/cable" host=myapp.herokuapp.com request_id=7752b409-3d26-4a82-9e39-73c34eb6819c fwd="90.109.65.65" dyno=web.1 connect=0ms service=170ms status=101 bytes=129
2016-04-23T23:26:37.090881+00:00 app[web.1]: Started GET "/cable" for 90.109.65.65 at 2016-04-23 23:26:37 +0000
2016-04-23T23:26:37.139914+00:00 app[web.1]: Started GET "/cable" [WebSocket] for 90.109.65.65 at 2016-04-23 23:26:37 +0000
2016-04-23T23:26:37.139965+00:00 app[web.1]: Successfully upgraded to WebSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: Upgrade, HTTP_UPGRADE: websocket)
2016-04-23T23:26:37.240234+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:121:in `call': ERR invalid password (Redis::CommandError)
2016-04-23T23:26:37.240241+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:102:in `block in connect'
2016-04-23T23:26:37.240242+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:293:in `with_reconnect'
2016-04-23T23:26:37.240243+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:100:in `connect'
2016-04-23T23:26:37.240244+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:276:in `with_socket_timeout'
2016-04-23T23:26:37.240246+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:133:in `call_loop'
2016-04-23T23:26:37.240246+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/subscribe.rb:43:in `subscription'
2016-04-23T23:26:37.240247+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/subscribe.rb:12:in `subscribe'
2016-04-23T23:26:37.240248+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:2760:in `_subscription'
2016-04-23T23:26:37.240248+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:2138:in `block in subscribe'
2016-04-23T23:26:37.240249+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:58:in `block in synchronize'
2016-04-23T23:26:37.240251+00:00 app[web.1]:    from /app/vendor/ruby-2.3.0/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
2016-04-23T23:26:37.240252+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:58:in `synchronize'
2016-04-23T23:26:37.240252+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:2137:in `subscribe'
2016-04-23T23:26:37.240253+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/actioncable-5.0.0.beta3/lib/action_cable/subscription_adapter/redis.rb:70:in `block in listen'
2016-04-23T23:26:37.240254+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis/client.rb:293:in `with_reconnect'
2016-04-23T23:26:37.240254+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:64:in `block in with_reconnect'
2016-04-23T23:26:37.240255+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:58:in `block in synchronize'
2016-04-23T23:26:37.240256+00:00 app[web.1]:    from /app/vendor/ruby-2.3.0/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
2016-04-23T23:26:37.240256+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:58:in `synchronize'
2016-04-23T23:26:37.240257+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:63:in `with_reconnect'
2016-04-23T23:26:37.240259+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/actioncable-5.0.0.beta3/lib/action_cable/subscription_adapter/redis.rb:67:in `listen'
2016-04-23T23:26:37.240259+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/redis-3.3.0/lib/redis.rb:70:in `without_reconnect'
2016-04-23T23:26:37.240261+00:00 app[web.1]:    from /app/vendor/bundle/ruby/2.3.0/gems/actioncable-5.0.0.beta3/lib/action_cable/subscription_adapter/redis.rb:141:in `block in ensure_listener_running'

非常感谢。

1 回复 | 直到 9 年前

Poilon 9 年前

好吧,我只是在这件事上浪费了很多时间。问题是,我只是把另一个redistogo子域搞得一团糟,同时又紧跟着一些例子。。。

配置/电缆.yml:

production: &production
  :url: redis://redistogo:MYREDISTOGOPASSWORD@lab.redistogo.com:10108/
  -------
  :host: tarpon.redistogo.com
  +++++++
  :host: lab.redistogo.com