Uncaught (in promise) Error: No QUIC connection available

[Kmtest-rgb]

Hi
I am trying to launch quic agent through owt server. I am building owt server with quic agent from source as described in

https://github.com/open-webrtc-toolkit/owt-server/blob/master/doc/design/quic-agent.md

I got a warning when running scripts/pack.js --t quic-agent -t all --install-module --app-path ${webrtc-javascript-sdk-sample-conference-dist}

Warning: /home/oct18_build/owt-server/source/agent/addons/quicIO/build/Release/quicIO.node not exist

Is this normal, because I am not sure if --t quicio-agent is needed ?

then when I launch the server, the quic-agent is not launched correctly . I get the following errors in the dist/logs/quic-xx_0.log

2021-10-18 22:07:00.024 - ERROR: InternalConnectionRouter - Internal connection router detected error {"purpose":"portal","id":"[email protected]","type":"worker"}

Is this because of the quicIO.node error before ?

Now when I go to https://hostname:3004.quic.html I get the same error as

open-webrtc-toolkit/owt-server#1058

I am launching chrome with

google-chrome --enable-experimental-web-platform-features

I am not sure why I am getting the same error.

I am using the prebuilt certificate.pfx which is in github. Do I need to extract the fingerprint from this certificate and add it to the javascript sdk client ?

Can you please help with this issues.

thanks

[jianjunz]

Hi,

It looks like WebTransport feature is not enabled at server side. If you successfully built QUIC agent, please modify management_api/management_api.toml, set enableWebTransport to true, and restart your server.

Verifying a certificate with hash only works for certificate valid for less than 14 days, you'll need to generate a new one with OpenSSL commands or the scripts in Chromium (ref: https://github.com/open-webrtc-toolkit/owt-server/blob/master/doc/design/quic-agent.md#generate-self-signed-certificates). A certificate issued by a trusted CA doesn't have the 14 days limitation.

QUIC IO is not required for WebTransport. It was a component for inter-agent transport.

[Kmtest-rgb]

Hi,

It looks like WebTransport feature is not enabled at server side. If you successfully built QUIC agent, please modify management_api/management_api.toml, set enableWebTransport to true, and restart your server.

Verifying a certificate with hash only works for certificate valid for less than 14 days, you'll need to generate a new one with OpenSSL commands or the scripts in Chromium (ref: https://github.com/open-webrtc-toolkit/owt-server/blob/master/doc/design/quic-agent.md#generate-self-signed-certificates). A certificate issued by a trusted CA doesn't have the 14 days limitation.

QUIC IO is not required for WebTransport. It was a component for inter-agent transport.

thanks for the reply Is the prebuilt Release version 5.0 https://github.com/open-webrtc-toolkit/owt-server/releases/tag/v5.0.1 supposed to work with webtransport or quic.

I changed the management_api.toml as you said . It launched quic_agent successfully .

But when I used the above test page quic.html, I got the same error.

Uncaught (in promise) Error: No QUIC connection available

I didnt modify any certificate, just used the certificate.pfx which came with release 5.0.
Am I supposed to generate my own certificate. I just want to check if it works for now.

the certificate.pfx which is in github is supposed to work atleast for 3 days right.

So I am not sure if the error is related to certificate or any other error . I am not sure if release 5.0 supports quic.html

thanks

[jianjunz]

v5.0 uses QuicTransport which is removed from WebTransport spec. It may not work with the latest browser. The main branch added support for WebTransport over HTTP/3.

[Kmtest-rgb]

v5.0 uses QuicTransport which is removed from WebTransport spec. It may not work with the latest browser. The main branch added support for WebTransport over HTTP/3.

Hi. Is there a big improvement when using webtransport over http/3 comparing to QuicTransport. For now we will be ok with QuicTransport also if it is stable and usable.

Is there any old version of browser which will work with version 5.0 quic server ?

If not is there any sample client like you have for webtransport , web_transport_test_client that you have for webtransport , Is there sample or test app we can use for server 5.0 ?

or do you suggest using everything from main branch ?

thanks