Skip to content

Conversation

@sahsanu
Copy link
Contributor

@sahsanu sahsanu commented Dec 8, 2025

Fixes #5184

Summary

This update improves WordPress Nginx templates, adds HTTP/3 support, and introduces automation for selective reuseport usage.

Changes

1. Added missing FastCGI parameter

  • Added fastcgi_param HTTP_HOST $host; to all WordPress-related Nginx templates.
  • Ensures correct host header forwarding to PHP-FPM and prevents URL resolution issues in WordPress.

2. Removed unused directive

  • Removed proxy_hide_header Upgrade; from multiple .stpl templates where it was not applicable to FastCGI setups.

3. New HTTP/3 WordPress templates and scripts

Introduced new templates and helper scripts with built-in HTTP/3 (QUIC) support:

  • wordpress-disable-xmlrpc-http3.sh
  • wordpress-disable-xmlrpc-http3.stpl
  • wordpress-disable-xmlrpc-http3.tpl
  • wordpress-http3.sh
  • wordpress-http3.stpl
  • wordpress-http3.tpl
  • wordpress_mu_subdir-http3.sh
  • wordpress_mu_subdir-http3.stpl
  • wordpress_mu_subdir-http3.tpl

4. Reuseport automation

  • Added scripts to automate enabling reuseport only for one site when multiple domains share the same IP, avoiding listener conflicts while supporting HTTP/3.

This update improves WordPress Nginx templates, adds HTTP/3 support, and introduces automation for selective `reuseport` usage.

- Added `fastcgi_param HTTP_HOST $host;` to all WordPress-related Nginx templates.
- Ensures correct host header forwarding to PHP-FPM and prevents URL resolution issues in WordPress.

- Removed `proxy_hide_header Upgrade;` from multiple `.stpl` templates where it was not applicable to FastCGI setups.

Introduced new templates and helper scripts with built-in HTTP/3 (QUIC) support:
- `wordpress-disable-xmlrpc-http3.sh`
- `wordpress-disable-xmlrpc-http3.stpl`
- `wordpress-disable-xmlrpc-http3.tpl`
- `wordpress-http3.sh`
- `wordpress-http3.stpl`
- `wordpress-http3.tpl`
- `wordpress_mu_subdir-http3.sh`
- `wordpress_mu_subdir-http3.stpl`
- `wordpress_mu_subdir-http3.tpl`

- Added scripts to automate enabling `reuseport` **only for one site** when multiple domains share the same IP, avoiding listener conflicts while supporting HTTP/3.

These changes improve compatibility, reliability, and performance for WordPress deployments on HestiaCP using Nginx + PHP-FPM.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Redirect error on WordPress enabling NGINX HTTP3

1 participant