HTTP/3 Support Issues

[dhia-gharsallaoui]

HTTP/3 Support Issues

Problem Description

Attempting to run HyperBEAM with HTTP/3 support encounters multiple configuration and runtime errors that prevent the server from starting successfully.

Environment

• Branch: edge
• Build Profile: http3
• Platform: Linux
• Erlang/OTP: 27.3

Issues Encountered

1. Missing quicer.app Dependency

Error:

{badmatch,{error,{quicer,{"no such file or directory","quicer.app"}}}}

Temporary Fix:
Adding quicer to the relx configuration resolves this issue, but this approach is not practical as it would include the dependency for all profiles where it's not needed.

2. TLS Configuration Error

After resolving the quicer dependency issue, the following errors occur:

Initial Error:

{{badmatch,{error,config_error,tls_error}},
 [{cowboy,'-start_quic/3-fun-3-',5,
          [{file,"/home/ubuntu/HyperBEAM/_build/default/lib/cowboy/src/cowboy.erl"},
           {line,96}]}]}

Application Exit:

=INFO REPORT==== 16-Jun-2025::14:10:29.337931 ===
    application: hb
    exited: {bad_return,
                {{hb_app,start,[normal,[]]},
                 {'EXIT',
                     {{badmatch,
                          {error,
                              {timeout,staring_http3_server,
                                  <<"Ws-ct6H1E8fezVzTXV84cMsIDwoyaHkzDTLqHWgS_kw">>}}},
                      [{hb_http_server,new_server,1,
                           [{file,"/home/ubuntu/HyperBEAM/src/hb_http_server.erl"},
                            {line,198}]},
                       {hb_http_server,start,1,
                           [{file,"/home/ubuntu/HyperBEAM/src/hb_http_server.erl"},
                            {line,111}]},
                       {hb_app,start,2,
                           [{file,"/home/ubuntu/HyperBEAM/src/hb_app.erl"},
                            {line,19}]},
                       {application_master,start_it_old,4,
                           [{file,"application_master.erl"},{line,295}]}]}}}}
    type: permanent

3. QUIC Listen Failure

Debug Output:

QUIC start config: [{alpn,["h3"]},
                    {peer_unidi_stream_count,3},
                    {peer_bidi_stream_count,100},
                    {certfile,"priv/cert.pem"},
                    {keyfile,"priv/cert.key"}]
Starting quicer:listen on port 58732 with opts: [{alpn,["h3"]},
                                                 {peer_unidi_stream_count,3},
                                                 {peer_bidi_stream_count,100},
                                                 {certfile,"priv/cert.pem"},
                                                 {keyfile,"priv/cert.key"}]
quicer:listen failed: {error,config_error,tls_error}

Final Error:

=ERROR REPORT==== 16-Jun-2025::15:09:06.708758 ===
Error in process <0.846.0> on node hb@ns31528130 with exit value:
{{badmatch,{error,config_error,{error,config_error,tls_error}}},
 [{hb_http_server,'-start_http3/3-fun-1-',3,
                  [{file,"/home/ubuntu/HyperBEAM/src/hb_http_server.erl"},
                   {line,224}]}]}

This is blocking the development of this device

Questions

1. Is HTTP/3 support fully implemented and ready for use?
2. Is there a specific branch where HTTP/3 functionality is working?
3. Are there additional configuration steps or dependencies required for HTTP/3 that aren't documented?

[samcamwilliams]

Hey @dhia-gharsallaoui !

The last time we used H3 it was working correctly with tests passing. It isn't part of our normal testing cycle though, as the Quic libraries make the build much less reliable between machines (as you seemed to experience). What was the exact dev environment that you were running on please? It is odd that the relx fixed it for you though. It should be possible to add the relx change to the rebar profile for just http3 though, so if it works for everyone there is a path forward there.

The TLS issue is likely to be due to some recent changes in Erlang. IIRC, they moved SSL versions, and some of the older releases required manual setup of TLS certs, rather than finding the host operating system's certs automatically. Do you still see this issue if you upgrade to Erlang OTP/28.0?

To the questions:

1. Yes, it should be. Thank you for raising the issue.
2. All (main, beta, edge), in theory.
3. These were not required when we last used it.

[dhia-gharsallaoui]

I tested with OTP27 and OTP28 on:

• Ubuntu 22.04.5 LTS

  • Kernel: Linux 5.15.0-134-generic
  • Architecture: x86-64

Additionally, I tested OTP27 on:

• Fedora Linux 42 (Workstation Edition)

  • Kernel: Linux 6.14.11-300.fc42.x86_64
  • Architecture: x86-64

In both cases, I encountered the same TLS issue. For reference, I performed the following steps:

1. Generated a new certificate using:

   openssl req -x509 -nodes -newkey rsa:2048 \
     -keyout priv/cert.key \
     -out priv/cert.pem \
     -days 365 \
     -subj "/CN=localhost" \
     -addext "keyUsage=keyEncipherment, digitalSignature" \
     -addext "extendedKeyUsage=serverAuth"

2. Updated the expired test certificates in hb_http_server.erl with the newly generated ones.