Subscriptions aren't getting acknowledged in Kubernetes Production environment

[Danieth]

Hey folks,

I've exhausted my resources here trying to figure out why I can't actually acquire a subscription to a channel, exclusively, in my production environment.

I'm deploying on DigitalOcean, with a very simple nginx configuration - which, has, had some issues websockets - however, I don't believe the connection itself is being severed in any way, primarily, because the client is receiving ping messages back.

It appears to me that, for some reason, RPC commands are just not hitting the rpc server in the Kubernetes environment vs run locally.

Javascript

I am using the AnyCable JS client (previously, the Rails ActionCable client -- same result)

Javascript Code

Production (Failing)

Local Development (Succeeding)

Network

In the network tab, it's clear, I'm receiving ping's from the anycable-go server!

Production (Failing)

Local Development (Succeeding)

Rails Code

There's nothing special happening on the backend. As far as I can tell (based on print out statements) the channel code is never actually being called in Production

Rails Channel Code

Rails Cable Code

Sever Logs

These are the Rails server logs, just for a single attempt to connect to the Server.

Production, Kubernetes instances (Failing)

Instances are roughly a 1:1 with the suggested helm file document: https://docs.anycable.io/deployment/kubernetes

stern anycable -t --since 10m

Local Development (Succeeding)

Procfile:

anycable-rpc: bundle exec anycable --log-grpc --debug
anycable-go:  anycable-go --port 8080 --log_level=debug

Redis

I confirmed with (connecting to dev and prod redis instances):

$redis.subscribe("__anycable__") do |on|
  on.subscribe do |channel, subscriptions|
    puts "Subscribed to ##{channel} (#{subscriptions} subscriptions)"
  end
  on.message do |channel, message|
    puts "##{channel}: #{message}"
    redis.unsubscribe if message == "exit"
  end
  on.unsubscribe do |channel, subscriptions|
    puts "Unsubscribed from ##{channel} (#{subscriptions} subscriptions)"
  end
end

that my messages are actually passing through the __anycable__ key for both development and production.

[Danieth]

Unfortunately, this was simply a manifestation of CloudFlares "websocket" option not being turned on

I simply, did not, realize that this setting had been disabled! Thanks!

[Envek]

Thanks for sharing the solution and for detailed description of the problem!