Getting System.Net.Quic is not supported on this platform on Linux #3664
-
Hi, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
You can turn on internal diagnostics for S.N.Quic: "Private.InternalDiagnostics.System.Net.Quic". For example, you can do that programmatically like this https://gist.github.com/ManickaP/864c3ee9c854db58db9ad6d54957d947, just change the If that doesn't show anything meaningful, the app cannot find and load libmsquic.so. So first step would be to locate it: In the end one of these cases will be the culprit:
|
Beta Was this translation helpful? Give feedback.
-
Hi, Thanks for your reply. I deleted my new CentOS 7 VM and tried with following steps:
On my other old VM which is CentOS 7, on this VM too MsQuic is working. On this VM when I run ldconfig -p | grep libmsquic, it shows following: linux-vdso.so.1 => (0x00007ffeac673000) I have another question, this link https://github.com/microsoft/msquic/blob/main/docs/Platforms.md describes that libmsquic requires Openssl 1.1, however, on my VMs as you can see above, it is also working with OpenSSL 1.0.2k-fips, or when I install libmsquic, it also installs Opensll 1.1 itself, is it correct? |
Beta Was this translation helpful? Give feedback.
The
ldd
command needs to be run with your location of libmsquic, so in your case /lib64/..., my example used location on my machine.As you can see the output of ldd, there is libcrypto 1.1 and that's what msquic needs. So it runs. The requirements mention OpenSSL 1.1, because that's the package that carries libcrypto 1.1.
And just FYI, CentOS 7 is rather old and will not be supported by .NET 8.