Fix Turbo::StreamsChannel::Error: Turbo::StreamsChannel refused connection for unauthorized user in Rails

This error occurs when a Turbo Streams broadcast channel refuses the WebSocket connection because the user is not authorized. Hotwire uses ActionCable for real-time updates and requires proper channel authorization. Ensure your Turbo::StreamsChannel subscription is verified and your signed stream names match between the broadcast and subscription.

Reading the Stack Trace

Here's what each line means:

• turbo-rails (1.5.0) app/channels/turbo/streams_channel.rb:18:in `subscribed': Turbo Streams channel rejects the subscription because the signed stream name verification failed.
• actioncable (7.1.3) lib/action_cable/channel/base.rb:146:in `subscribe_to_channel': ActionCable processes the subscription request and the channel rejects it.
• app/views/posts/show.html.erb:3:in `_app_views_posts_show_html_erb__render': The view uses turbo_stream_from which initiates the WebSocket subscription.

Common Causes

# View subscribes to:
<%= turbo_stream_from @post %>

# But broadcast sends to a different stream:
Turbo::StreamsChannel.broadcast_append_to(
  'all_posts',  # Different from @post stream
  target: 'comments',
  partial: 'comments/comment'
)

# app/channels/application_cable/connection.rb
module ApplicationCable
  class Connection < ActionCable::Connection::Base
    # No authentication - current_user is nil
  end
end

# Gemfile includes turbo-rails but cable.yml uses async adapter
# config/cable.yml
production:
  adapter: async  # Broadcasts won't work across processes

The Fix

Ensure the turbo_stream_from helper and the broadcast target use the same streamable object. Using the model instance directly ensures the signed stream names match between the subscription and the broadcast.

<%= turbo_stream_from 'all_posts' %>

# Broadcasting to mismatched stream:
Turbo::StreamsChannel.broadcast_append_to(
  @post,
  target: 'comments',
  partial: 'comments/comment'
)

<%= turbo_stream_from @post %>

# Model with broadcasts:
class Comment < ApplicationRecord
  belongs_to :post
  after_create_commit -> {
    broadcast_append_to post, target: 'comments',
      partial: 'comments/comment'
  }
end

Testing the Fix

require 'rails_helper'

RSpec.describe 'Turbo Stream broadcasts', type: :system do
  let(:post) { create(:post) }

  it 'broadcasts new comments to the post stream' do
    visit post_path(post)
    expect(page).to have_css('#comments')

    comment = create(:comment, post: post, body: 'Live comment!')
    expect(page).to have_content('Live comment!')
  end
end

RSpec.describe Comment, type: :model do
  it 'broadcasts after creation' do
    post = create(:post)
    expect {
      create(:comment, post: post, body: 'Test')
    }.to have_broadcasted_to(post)
  end
end

Run your tests:

bundle exec rspec spec/models/comment_spec.rb spec/system/turbo_stream_spec.rb

Pushing Through CI/CD

git checkout -b fix/rails-hotwire-broadcast,git add app/models/comment.rb app/views/posts/show.html.erb,git commit -m "fix: align Turbo Stream broadcast and subscription targets",git push origin fix/rails-hotwire-broadcast

Your CI config should look something like this:

name: CI
on:
  pull_request:
    branches: [main]
jobs:
  test:
    runs-on: ubuntu-latest
    services:
      postgres:
        image: postgres:16
        env:
          POSTGRES_PASSWORD: postgres
        ports: ['5432:5432']
      redis:
        image: redis:7
        ports: ['6379:6379']
    steps:
      - uses: actions/checkout@v4
      - uses: ruby/setup-ruby@v1
        with:
          ruby-version: '3.3'
          bundler-cache: true
      - run: bin/rails db:setup
      - run: bundle exec rspec

The Full Manual Process: 18 Steps

Here's every step you just went through to fix this one bug:

1. Notice the error alert or see it in your monitoring tool
2. Open the error dashboard and read the stack trace
3. Identify the file and line number from the stack trace
4. Open your IDE and navigate to the file
5. Read the surrounding code to understand context
6. Reproduce the error locally
7. Identify the root cause
8. Write the fix
9. Run the test suite locally
10. Fix any failing tests
11. Write new tests covering the edge case
12. Run the full test suite again
13. Create a new git branch
14. Commit and push your changes
15. Open a pull request
16. Wait for code review
17. Merge and deploy to production
18. Monitor production to confirm the error is resolved

Total time: 30-60 minutes. For one bug.

gem install bugstack

require 'bugstack'

Bugstack.init(api_key: ENV['BUGSTACK_API_KEY'])

Deploying the Fix (Manual Path)

1. Align broadcast and subscription stream names.
2. Configure Redis for ActionCable in production.
3. Add system and model specs for broadcasts.
4. Open a pull request.
5. Merge and verify real-time updates work in staging.

Frequently Asked Questions