sribe
[error] Ranch protocol :error (:cowboy_protocol) of listener UrlFetcher.Endpoint.HTTP terminated
** (exit) :undef
15:07:19.288 [error] Ranch listener ‘Elixir.UrlFetcher.Endpoint.HTTP’ connection process start failure; cowboy_protocol:start_link/4 crashed with reason: error:undef
Any idea where to look? I have renamed some files & modules, which is of course an immediate suspect for this error. But I’ve double-checked everything; deleted the _build folder; and I don’t see anything wrong in the project.
(I have added gRPC modules; but I don’t see how they could affect this.)
Trending in Questions
Hello everyone!
I am new to coding with Elixir/Erlang. And i am looking for some utilities for fuzzing testing like AFL++.
Does anyone ...
New
I’m very new to Elixir, so sorry if this is a silly question:
I am wondering what happens to the mailbox of a process when the machine i...
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
Background
When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error:
* assembling mark...
New
I load tested a plain Phoenix chat app backed by Postgres with 100 million messages in it, everything on default settings, to see what br...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #elixirconf-us
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #security
- #elixirconf-eu
- #processes
- #api
- #forms
- #hex











Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
OvermindDL1
Huh, that is entirely new to me. Any chance on posting this project on github or preferably a simplified version that reproduces this error?
sribe
Going through my changes step-by-step: it’s caused by the Cowboy branch from Tony Han as part of his gRPC support.
So I’m going to dig into that repo and look at his commits now.
sribe
The plug/phoenix forks do not work with the gRPC stuff straight out of the box, and I don’t think I can take the time right now to fix that.
I’m trying to implement a super-simple API (1 call), so I think my best bet is probably to start with gRPC, then set up routing of my 1 endpoint from Cowboy to a handler, without Phoenix & Plug.
OvermindDL1
Oh I hope that adds HTTP2 support… >.<
We need a way in phoenix to specify to the plug to send other data/files to the client along with the page (page first though) ahead-of-time…
sribe
Yes, Cowboy 2 adds HTTP2 support, and that is in fact the source of the API incompatibility–new HTTP features.
tony612
Hi, just saw this. I just use the commit in this PR to support Trailers in HTTP/2 http trailers support by IgorKarymov · Pull Request #1020 · ninenines/cowboy · GitHub . But I don’t think it’s related to your problem. And maybe it’s not a good idea to use Cowboy2 with Phoenix before the stable version is released.
seeekr
What’s the status of cowboy 2.x with phoenix? I’m trying to use your grpc library in a phoenix 1.3 project, getting "ranch protocol :error"s.
OvermindDL1
Current Plug/Phoenix master has Cowboy2 support, they are just finishing refining it but you can use it now if you want to play with it.
Darim
How exactly should they all be specified in mix.exs?
OvermindDL1
Use the master versions, they have not had a release yet.