• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved http/3 supported by plesk?

AYamshanov said:
If you use nginx as a proxy for apache (or nginx-only option), nginx will able to serve HTTP3 requests.

If you upgrade a server from the previous Plesk version, you need to enable the feature through CLI.
Code: 
plesk bin http3_pref --enable -panel -nginx

HTTP/3 uses UDP protocol. If you have a firewall (on a server level and/or on the cloud infrastructure level), you need to allow incoming connections to 443/udp, 8443/udp ports.

You can try to check if your server announced the ability to connect to it through HTTP/3 or not,
  • with an external tool like HTTP/3 Check,
  • with a browser's dev.consone like on the screenshot,
View attachment 26183


Only if you use apache without nginx in front of it (or IIS in Plesk for Windows), it will not be possible to serve HTTP3 requests.
Currently, as I know, apache does not support HTTP3, 64462 – [Feature Request] Support for HTTP/3.
Click to expand...
plesk bin http3_pref --enable -panel -nginx
Execution failed.
Command: pleskrc
Arguments: Array
(
[0] => sw-cp-server
[1] => try-reload
)

Details: Job for sw-cp-server.service failed.
See "systemctl status sw-cp-server.service" and "journalctl -xeu sw-cp-server.service" for details.
 
I activated with
Code: 
plesk bin http3_pref --enable
but now the Plesk login page never let me login as it not loads on port 8443.
I cannot log in anymore on Plesk after the command to enable http 3
 
The issue seems caused by the enable HTTP 3 command that generate the issue of
Details: Job for sw-cp-server.service failed.
See "systemctl status sw-cp-server.service" and "journalctl -xeu sw-cp-server.service" for details.

Reboot server never help.
Try to restart service give errors so I'm cut of my production Plesk server
Code: 
service sw-engine restart && service sw-cp-server restart
Job for sw-cp-server.service failed because the control process exited with error code.
See "systemctl status sw-cp-server.service" and "journalctl -xeu sw-cp-server.service" for details.

Code: 
systemctl status sw-cp-server.service
● sw-cp-server.service - Startup script for Plesk control panel server
     Loaded: loaded (/lib/systemd/system/sw-cp-server.service; enabled; vendor preset: enabled)
    Drop-In: /usr/lib/systemd/system/sw-cp-server.service.d
             └─respawn.conf
     Active: activating (auto-restart) (Result: exit-code) since Wed 2024-05-15 16:05:31 CEST; 4s a>
    Process: 57787 ExecStartPre=/usr/sbin/sw-cp-serverd -q -t (code=exited, status=1/FAILURE)
        CPU: 10ms

Code: 
The job identifier is 67752 and the job result is done.
May 15 16:06:24 mydomain.it systemd[1]: Starting Startup script for Plesk control panel server.>
░░ Subject: A start job for unit sw-cp-server.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit sw-cp-server.service has begun execution.
░░
░░ The job identifier is 67752.
May 15 16:06:24 mydomain.it sw-cp-serverd[58037]: nginx: [emerg] duplicate listen options for 0>
May 15 16:06:24 mydomain.it sw-cp-serverd[58037]: nginx: configuration file /etc/sw-cp-server/c>
May 15 16:06:24 mydomain.it systemd[1]: sw-cp-server.service: Control process exited, code=exit>
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStartPre= process belonging to unit sw-cp-server.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
May 15 16:06:24 mydomain.it systemd[1]: sw-cp-server.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit sw-cp-server.service has entered the 'failed' state with result 'exit-code'.
May 15 16:06:24 mydomain.it systemd[1]: Failed to start Startup script for Plesk control panel >
░░ Subject: A start job for unit sw-cp-server.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit sw-cp-server.service has finished with a failure.
░░
░░ The job identifier is 67752 and the job result is failed.
 
Could you please post the output of the command `plesk version`?

PeopleInside said:
duplicate listen options for 0>
Click to expand...
With arrows on the keyboard, it should be possible to show the hidden text on the right side (e.g. a filename/line should have been logged).

Also, you can try to regenerate the configs with the command `plesk sbin httpdmng --reconfigure-server` or `plesk repair web`
And/or disable the HTTP/3 feature with the command `plesk bin http3_pref --disable` to make the Plesk web interface available (if the issue is related to the HTTP3 feature).
 
Do plesk repair seems never resolve.
Disable http 3 never resolve.

I'm contacting the Plesk support by reacing you with a ticket or chat.
This HTTP 3 broke my Plesk.
 
Hello, I followed procedure for enabling HTTP3 and successfully enabled by the command in ssh, accepted 2 new rules in plesk firewall to be applied,
HTTP/3 Check says that QUIC is supported for all domains, but in Chrome and FF DEV in network tab i still get h2 and not h3 as expected.
I have tried as well to do plesk bin http2_pref --disable and now i get h1.1 in dev console..
What should i do to see h3 in console???
TLS cyphers are on intermediate since i need tls 1.2 for ftp client, but tls1.3 should be used for web, no?
All checked domains use nginx only, not apache.

Please help!!! Thank you!
 
The issue happens because a directive is not properly removed when enabling http3:
Code: 
May 15 17:16:34 domain.ext sw-cp-serverd[106784]: nginx: [emerg] duplicate listen options for 0.0.0.0:8443 in /etc/sw-cp-server/conf.d/http3_plesk.inc:1
The support restored Plesk interface with the command
Code: 
plesk bin http3_pref --disable -panel -nginx

and is now checking why this issue happen.

After investigation ends we will try to enable HTTP 3 for Plesk and for all websites.
 
arriterx said:
I have tried as well to do plesk bin http2_pref --disable and now i get h1.1 in dev console..
Click to expand...
You do not need to disable http2_pref, makes sense to enable it back. When HTTP2 and HTTP3 are available, a browser decides what protocol to use. Do you use an actual version of a browser? As an example, you can try to run a browser in "Incognito mode", sometimes it helps me.
 
AYamshanov said:
You do not need to disable http2_pref, makes sense to enable it back. When HTTP2 and HTTP3 are available, a browser decides what protocol to use. Do you use an actual version of a browser? As an example, you can try to run a browser in "Incognito mode", sometimes it helps me.
Click to expand...
tried everything, incognito as well, still get H2 on all domains....and i cant restart the server :(:(:(:(
 
PeopleInside said:
What hosting are you using?
Have you checked if the hosting has the Firewall rule to allow UDP 443 port?
Have you also checked Plesk Firewall to check if a banner say you need do actions to apply new rules introduced with HTTP 3 ?
Click to expand...
I use Aruba Italian ISP dedicated server
I do not have any hw firewalls in front of my server
Yes, I have applied 2 rules to allow QUIC appeared after I have enabled http3
 
@arriterx in my case the hosting is IONOS and they have a Firewall.
I need to create a rule to allow HTTP 3 port 443 and now I pass the check at https://http3check.net also if ... is very strange but browsers seems are not using or preferring HTTP 3. Very strange... so I'm happy to have activated with the help of the Plesk support team by opening a ticket where we are investigating an issue but currently I don't see the great speed increasing and the browser developer console still showing that use HTTP 2 :D even on some website not Plesk but that should use HTTP 3.

Ok I don't know how to help but I replied to you just to be sure you don't need add a firewall rule to see the http 3 test passed.
 
PeopleInside said:
@arriterx in my case the hosting is IONOS and they have a Firewall.
I need to create a rule to allow HTTP 3 port 443 and now I pass the check at https://http3check.net also if ... is very strange but browsers seems are not using or preferring HTTP 3. Very strange... so I'm happy to have activated with the help of the Plesk support team by opening a ticket where we are investigating an issue but currently I don't see the great speed increasing and the browser developer console still showing that use HTTP 2 :D even on some website not Plesk but that should use HTTP 3.

Ok I don't know how to help but I replied to you just to be sure you don't need add a firewall rule to see the http 3 test passed.
Click to expand...
Thank you very much for your effort!
It seems queit strange as well for me, I have tested FF Dev, FF normal, Chrome, Edge, all updated to latest versions and noone is able to connect to any of domains hosted on my server in HTTP3 while all domains pass http3 verification on HTTP/3 Check as well as on Cloudflare http3 test page.
I know that my browsers are capable of negotiating http3 since other sites like cloudflare or google work always in http3...

What is happening, idk :(
Or maybe i do not understand how http3 actually works or miss something....
I need http3 for big chunk file uploads speed improvements which should be great, since http2 is known for bottlenecking http uploads and thus half of planet wants to implement http3 to improve uploads instead of using old http1.1 like aws s3 does.
 
Is the same for me. I don't understand as well :) while also Facebook seems is not loading in HTTP 3 also Cloud flare etc :) not only my Plesk website that are now passing the test. I don't know
 
AYamshanov said:
If you use nginx as a proxy for apache (or nginx-only option), nginx will able to serve HTTP3 requests.

If you upgrade a server from the previous Plesk version, you need to enable the feature through CLI.
Code: 
plesk bin http3_pref --enable -panel -nginx

HTTP/3 uses UDP protocol. If you have a firewall (on a server level and/or on the cloud infrastructure level), you need to allow incoming connections to 443/udp, 8443/udp ports.

You can try to check if your server announced the ability to connect to it through HTTP/3 or not,
  • with an external tool like HTTP/3 Check,
  • with a browser's dev.consone like on the screenshot,
View attachment 26183


Only if you use apache without nginx in front of it (or IIS in Plesk for Windows), it will not be possible to serve HTTP3 requests.
Currently, as I know, apache does not support HTTP3, 64462 – [Feature Request] Support for HTTP/3.
Click to expand...
FWIW - We have 2 identical cloud servers, provided by IONOS (spec as per forum signature). We had no issues implementing HTTP3, as per this ^ post (& its predecessor). In our case, we had to enable ports 443 and 8443 to allow incoming udp connections on each cloud server & then also enable them again, within our Danami Juggernaut (firewall which negates the use of the Plesk firewall) on each cloud server. It worked perfectly, first time, exactly as intended, on both. Many of the HTTP3 test sites are actually not that consistent: Pass / Fail / Pass / Pass etc but checking / testing HTTP3 using either a browser's Dev Panel (as is shown in the post above) or via CLI / Curl etc, shows HTTP3 results, clearly and consistently. For those having issues, it may just be local config that's at fault.
 
You must log in or register to reply here.

Similar threads

P
Question NGINX HTTP3 with Multiple Workers
Replies
4
Views
916
andreios
andreios
M
Issue Cannot bring http3 to domains.
Replies
14
Views
2K
MartinT
M
F
Resolved HTTP 3 is not used despite NGINX Only hosting
2
Replies
23
Views
2K
MartinT
M
P
Issue HTTP3 does not work in NGINX only server
Replies
10
Views
1K
learning_curve
learning_curve
Ankebut
Resolved Issue with HTTP/3 Activation on WOLTLAB Forum Administration
Replies
14
Views
2K
Ankebut
Ankebut
Back
Top