Closed AndrwM closed 1 year ago
Looks like you're trying to connect to Rails Action Cable server
This line indicates that your clients try to connect to the built-in Action Cable server; can you show the contents of the "Headers" tabs from the browser console? What is the URL?
How do you configure the client? Do you use the action_cable_meta_tag
to inject the URL into an HTML or maybe you provide an explicit URL value to the createConsumer
function?
It looks like we misconfigured ingress. Previously we had cargo-culted pathType: ImplementationSpecific
and for port name: use-annotation
but when we swapped this for pathType: Exact
and for port number: 8080
, we were able to see traffic in the logs of anycable-go
pod!!
I think you can close this, sorry for the noise and thank you so much for the responses ❤️
Tell us about your environment
Ruby version: 2.7.7
Rails version: 6.0.6
anycable
gem version: 1.3.0anycable-rails
gem version: 1.3.7grpc
gem version: 1.54.2What did you do?
We run a k8s cluster and are using the helmchart to run anycable-go (this seems fine) but we’re using kustomize to configure our anycable rpc server and we’re seeing an error that we haven't been able to find any mention to in any anycable docs, issues, or discussions. Worth noting we are running Alpine.
Here's our configuration
What did you expect to happen?
anycable-rpc should start without creshing
What actually happened?
(1) anycable-rpc is crashing with an output of:
(2) We see a websocket connection in the frontend:
identifier
back(3) We're seeing logs of
(4) We're seeing Rails logs from the ActionCable channels indicating that a subscription has occurred success
(5) Within the Rails console we are seeing that AnyCable is enabled
We're unable to find additional logging or information on the anycable-rpc issue and we're hopeful someone in the community may know where to look. 🤝 🙏 Thanks for your time.