I read this thread Will there be support for http3? - #12 by sahsanu, and I offer my config under WordPress. I have 3 sites, everything is fine and without errors. The check shows both in the console and online that http3 is supported. Perhaps someone will add something else. Thank you for your attention
I mean the same ip in your server. I’m asking because this is what happens when you use reuseport in two different sites sharing the same listen ip:
# nginx -t
nginx: [emerg] duplicate listen options for 203.0.113.1:443 in /etc/nginx/conf.d/domains/example.net.ssl.conf:7
nginx: configuration file /etc/nginx/nginx.conf test failed
Also, I don’t know what is the nginx version you are using but since version 1.25.1 the use of http2 in listen directive is deprecated, it must be added as http2 on; directive and Hestia adds it to a conf file.
nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
root@rgkpwsgxjj:~# nginx -v
nginx version: nginx/1.27.0
systemctl status nginx
● nginx.service - nginx - high performance web server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; preset: enabled)
Active: active (running) since Tue 2024-07-30 23:18:26 MSK; 4s ago
Docs: https://nginx.org/en/docs/
Process: 39940 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=0/SUCCESS)
Main PID: 39942 (nginx)
Tasks: 4 (limit: 1139)
Memory: 5.6M
CPU: 29ms
CGroup: /system.slice/nginx.service
├─39942 "nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf"
├─39943 "nginx: worker process"
├─39944 "nginx: cache manager process"
└─39945 "nginx: cache loader process"
июл 30 23:18:26 rgkpwsgxjj systemd[1]: Starting nginx.service - nginx - high performance web server...
июл 30 23:18:26 rgkpwsgxjj systemd[1]: nginx.service: Can't open PID file /run/nginx.pid (yet?) after start: No such file or directory
июл 30 23:18:26 rgkpwsgxjj systemd[1]: Started nginx.service - nginx - high performance web server.
The listen directive can have several additional parameters specific to socket-related system calls. These parameters can be specified in any listen directive, but only once for a given address:port pair.
So, socket parameters like reuseport can only be used for an address:port, if you use it in several server blocks, you should get the error I posted previously so I don’t know what’s going on here I also use Nginx 1.27.0.
Are you sure you are not using different internal/private ips and nated the public ip?
No), I deliberately posted all the screenshots, configs and so on, just in case I miss something, I wanted to shoot another video, but I restrained myself. Perhaps you will have some kind of thought, what information confirms this, and I will send it to you). That is, once again I have the same IP VDS server for the panel, this is natural, and accordingly for the sites. Perhaps if you download the config for yourself, you will not have an error, for example, on 2 test sites
I’ve edited your post to replace the real ip by 203.0.113.160.
Well, you didn’t apply your wordpress template to your sites and that is the reason you see no errors regarding duplicated listen directives using reuseport.
Now I’ve just changed the template to WordPress, and again I see http3, apparently you’re right, CF does it itself. To apply the template, I use
v-rebuild-users
And also go to the panel, and change the template from WordPress to site + vorpress
And it has always been used before)
Well, how can I do it right now, leave it on one site