Resolved http3 issue with Angular app

[igorosabel]

Server operating system version

Debian 11.11

Plesk version and microupdate number

18.0.66 #2

Hi!

I have an issue with nginx, http3 and Angular apps. I activated http3 support on nginx using the CLI:

plesk bin http3_pref --enable

After that I checked:
root@server:/home/user# plesk bin http3_pref --status
HTTP/3 is enabled for nginx

When I check with HTTP/3 Check it says:

Server does not advertise any alternative services.

I have an Angular app on a domain and since it's all static files (html, css and js) I have only nginx activated for the site:

Proxy mode: unchecked
Intelligent processing of static files: unchecked
Serving static files directly using nginx: checked
Additional nginx directives

location ~ ^/ {
try_files $uri $uri/ /index.html;
}
location = /index.html {
internal;
add_header Cache-Control "no-store, no-cache, must-revalidate";
}

I also have the Firewall Plesk extension but I have a rule that says "WWW server usign HTTP/3" and "Plesk administrative interface using HTTP/3".

Using Chrome Developer Tools I see that every asset requested from the app (like other js files or images) have this header:

Alt-Svc: h3=".443"; ma=86400

But the main file has the header missing. Why is this? Am I missing something?

Thanks!

 

[Sebahat.hadzhi]

Alt-Svc indicates that Nginx is serving http3 and it could be accessed via http3. Could you please confirm if the test you are running matches the preferred domain name value in Hosting & DNS > Hosting, i.e. if it is www.example.com, do you run the test for Example Domain ?

 

[igorosabel]

Yes, in Hosting & DNS > Hosting I just have the domain, without the "www". I can access the site typing "Indomable" and nothing is added nor redirected. I have checked "Redirect visitors from HTTP to HTTPS using an SEO-friendly 301 redirect" but if I enter the address with the https there are no redirects.

On HTTP/3 Check I have tried the "advanced" tab, where I put the IP address of the server, the port (443) and the host name (just indomablestore.com without anything else) and it says:
HTTP/3 Check could not get the server's advertised QUIC versions due to the error given below.

Server does not advertise any alternative services.

HTTP Header

HTTP/1.1 200 OK
Server: nginx
Date: Mon, 13 Jan 2025 10:30:20 GMT
Content-Type: text/html
Content-Length: 7064
Last-Modified: Thu, 09 Jan 2025 22:06:07 GMT
Connection: keep-alive
ETag: "6780484f-1b98"
Cache-Control: no-store, no-cache, must-revalidate
Accept-Ranges: bytes

Thanks for the response, if there is anything else I should look please tell me.

 

[learning_curve]

~~ On HTTP/3 Check I have tried the "advanced" tab, where I put the IP address of the server, the port (443) and the host name (just indomablestore.com without anything else) and it says ~~

It does. It also fails on many other HTTP/3 "Online Tests" too
e.g. http/3 test – test your connection & boost your own website or HTTP/3 checker {Free & Online SEO Tool}✴️ and many, many others...

Thanks for the response, if there is anything else I should look please tell me.

The good news, is that simple curl tests for HTTP/3 via CLI ( for which, you'll need to use a version of curl that supports HTTP/3 as not all do - yet ) shows that HTTP/3 on the domain that you've mentioned above (on its associated IP address), is fine:

curl --http3 https://indomablestore.com -I

and/or

curl -vDI https://indomablestore.com --http3-only

Excluding the https:// prefix: ( $ curl --http3 indomablestore.com -I for example ) just confirms your HTTP to HTTPS SEO-friendly 301 redirect as expected

Not posted the specific test results here, as you can quickly run these tests yourself for clarity, but the Plesk enable command

plesk bin http3_pref --enable

does NOT appear to be the cause of the issues that you're having with online HTTP/3 tests, as HTTP/3 when tested via curl, appears to be fully functional.

One common error is using browsers / devices that don't support QUIC hence false negative online test results
Assuming that ^ is not applicable in your case, then the true cause, is elswhere in your server / Plesk config

 

[igorosabel]

Ok, since it seems to be an issue with the HTTP/3 checkers I'll leave it be. Thanks!