rmdashrfv
commented
2 years ago Upgrading the Heroku Stack from 20 to 22, and ruby version from 3.0.3 to 3.1.2 didn't help in any way.
Closed rmdashrfv closed 2 years ago
rmdashrfv
commented
2 years ago Upgrading the Heroku Stack from 20 to 22, and ruby version from 3.0.3 to 3.1.2 didn't help in any way.
rmdashrfv
commented
2 years ago I was able to get this error fixed and the process itself to actually run. But the issue is now that Heroku does not support HTTP/2. AnyCable cannot run on Heroku no matter what you do. Don't waste your time folks!
palkan
commented
2 years ago Please, read the documentation carefully.
AnyCable runs on Heroku without any problems. Proved by many production installations. Our demo application also runs on Heroku (latest stack): https://demo.anycable.io/
rmdashrfv
commented
2 years ago @palkan I can send you a video of following the documentation carefully. As you're aware, it doesn't take long to get set up. So far, every engineer I talk to has told me that it's not possible. And after following the docs, I don't know what else to say about it. Happy to update my comment though, if I find otherwise.
I think even the Procfile didn't have the intended effect on Heroku? Or was that just me?
palkan
commented
2 years ago It's not possible to have HTTP2 on Heroku accessible from the outside. But no one can stop us from using it within a dyno. From the docs:
The only way (for now) to run AnyCable applications on Heroku is to have two separate applications sharing some resources: the first one is a typical web application responsible for general HTTP and the second contains AnyCable WebSocket and RPC servers.
"every engineer" != "every good engineer"
I think even the Procfile didn't have the intended effect on Heroku?
My app uses the same Procfile as in the docs; you can find the source code here: https://github.com/anycable/anycable_rails_demo/pull/4
From the exception, it seems that gRPC server tried to listen on the 0.0.0.0. Since you don't specify this address in the Procfile, it could be either defined via env (ANYCABLE_RPC_HOST=0.0.0.0:50051) or in the YML config (or explicitly in the code).
The default value is "127.0.0.1".
You can debug configuration by running the following command: heroku run "bundle exec rails runner 'pp AnyCable.config'" -a your-rpc-app.
rmdashrfv
commented
2 years ago I was able to get the process to spin up and listen with this as the web command in the Procfile:
web: ANYCABLE_DEBUG=1 bundle exec anycable --server-command="anycable-go --host=0.0.0.0 --port=$PORT" --rpc-host="0.0.0.0:50051"
If I'm not mistaken, that should satisfy the "ANYCABLE_RPC_HOST" variable requirement. Once I added this, I can confirm that the process spun up properly in debug mode and was listening correctly.
The issue that made me (and others) determine that we weren't able to do it on Heroku was that when a message was sent, it wouldn't actually deliver messages to the client. This is the error that would occur:
2022-07-31T19:45:28.805798+00:00 app[web.1]:
E 2022-07-31T19:45:28.805Z context=ws Websocket session initialization failed: rpc error: code =
Unavailable desc = last connection error: connection error: desc =
"transport: Error while dialing dial tcp: address 0.0.0.0: missing port in address"But it did actually receive the message itself:
D 2022-08-01T00:21:09.013Z context=pubsub Incoming pubsub message from Redis: { ...message_data }I'm not sure why there's this remaining problem? "Unavailable context=rpc RPC failure: last connection error: connection error: desc = "transport: Error while dialing dial tcp: address 0.0.0.0: missing port in address"
I'll definitely try again. By the way you make it sound, I was close to having it done before I took everything down?
palkan
commented
2 years ago address 0.0.0.0: missing port in address
The error says that is says: the RPC address value for anycable-go is invalid, it must include a port as well. Do you the ANYCABLE_RPC_HOST config var set? You should remove it (as well as --rpc-host="0.0.0.0:50051"). The default values should be enough.
palkan
commented
2 years ago Which anycable-go version do you run?
rmdashrfv
commented
2 years ago I do have ANYCABLE_RPC_HOST config var set (as well as ANYCABLE_HOST), both of which were "0.0.0.0".
I'll remove --rpc-host="0.0.0.0:50051" as well.
I was running the default version. IIRC 1.1.0?
rmdashrfv
commented
2 years ago Hm. It must have been either the addition of --rpc-host="0.0.0.0:50051" or having the ANYCABLE_RPC_HOST variable overwriting something with 0.0.0.0.
It does in fact work now.
Using anycable-go 1.1.0.
"every engineer" != "every good engineer" indeed 🤷♂️
rmdashrfv
commented
2 years ago @palkan can you remove the invalid tag. This has been solved.
Thank you very much!
Tell us about your environment
Ruby 3.0.3 Rails 7.0.3.1
Gem versions: anycable 1.2.3 anycable-rails ~> 1.3, >= 1.3.4 grpc ~> 1.37
What did you do?
Tried to deploy to Heroku after following the documentation exactly. Using the procfile provided at the top. https://docs.anycable.io/deployment/heroku?id=heroku-deployment
What did you expect to happen?
The AnyCable server should start and begin listening on the heroku app, as it does in development environments. This is what happens when I run the command locally:
What actually happened?
The app crashes upon starting. It appears as though there's some issue binding the address
0.0.0.0in production. Is this due to Heroku not supporting HTTP/2? Or should I pass the--rpc-hostflag something very specific? I have been trying to deploy by passing the --rpc-host flag various things and none of them seem to work.It could be that as Heroku has updated their system, this configuration is no longer allowed? Perhaps downgrading my Heroku stack from 20 to a lower number?