Apache 2.4.66 on Windows 11 fails after creating a site: Invalid command 'ProxyFCGIBackendType'

[eloimarquessilva]

Environment

• Application: FlyEnv-Portable-4.13.3
• OS: Windows 11 Pro
• Web Server: Apache 2.4.66

Description

When using Apache 2.4.66 in FlyEnv-Portable-4.13.3 on Windows 11 Pro, simply creating a new site is enough to trigger an Apache startup failure.

This is reproducible even with a static site. No PHP framework or application setup is required.

After creating the site, FlyEnv shows the following error:

Error: AH00526: Syntax error on line 19 of C:/FlyEnv/FlyEnv-Data/server/vhost/apache/flyenv-test-xzp0dj47.test.conf:
Invalid command 'ProxyFCGIBackendType', perhaps misspelled or defined by a module not included in the server configuration

Steps to reproduce

1. Open FlyEnv-Portable-4.13.3
2. Install or select Apache 2.4.66
3. Create any new site
4. The site can be completely static
5. Try to start Apache

Expected behavior

Apache should start normally after creating the site.

Actual behavior

Apache fails to start and FlyEnv reports:

AH00526: Syntax error on line 19 of C:/FlyEnv/FlyEnv-Data/server/vhost/apache/flyenv-test-xzp0dj47.test.conf:
Invalid command 'ProxyFCGIBackendType', perhaps misspelled or defined by a module not included in the server configuration

Reproduction notes

• The issue happens with a minimal setup
• No PHP project is needed
• No additional configuration is needed
• Creating a site alone is enough to reproduce the problem

Possible cause

It looks like the generated Apache vhost configuration includes the directive ProxyFCGIBackendType, but the Apache build/configuration used by FlyEnv does not have the required module loaded or does not support that directive in the current setup.

This may be caused by:

• a missing Apache module
• an incompatible vhost template for Apache 2.4.66 on Windows
• a packaging/configuration issue in the bundled Apache environment

Additional context

Since this happens even with a static site, the problem appears to be related to the generated vhost/config template rather than to user application code.

[xpf0000]

The issue has been resolved.
The cause was a change in the configuration file format of the newer Apache version, which prevented required modules from being enabled during startup. The latest version has addressed this issue.

old format:

#LoadModule headers_module
#LoadModule deflate_module

new format:

# LoadModule headers_module
# LoadModule deflate_module

Two solutions:

1. Upgrade to the latest version, then in the Apache panel's configuration file tab, open the directory where the configuration files are located, delete the contents, and restart Apache.
2. Manually enable the required modules.

# LoadModule headers_module => LoadModule headers_module
# LoadModule deflate_module => LoadModule deflate_module
# LoadModule proxy_module => LoadModule proxy_module
# LoadModule proxy_fcgi_module => LoadModule proxy_fcgi_module
# LoadModule ssl_module =>  LoadModule ssl_module
# LoadModule access_compat_module => LoadModule access_compat_module
# LoadModule rewrite_module => LoadModule rewrite_module
# ServerName www.*** => ServerName www.*** 

https://github.com/xpf0000/FlyEnv/releases/tag/v4.13.4

[eloimarquessilva]

Two solutions:

1. Upgrade to the latest version, then in the Apache panel's configuration file tab, open the directory where the configuration files are located, delete the contents, and restart Apache.
2. Manually enable the required modules.

# LoadModule headers_module => LoadModule headers_module
# LoadModule deflate_module => LoadModule deflate_module
# LoadModule proxy_module => LoadModule proxy_module
# LoadModule proxy_fcgi_module => LoadModule proxy_fcgi_module
# LoadModule ssl_module =>  LoadModule ssl_module
# LoadModule access_compat_module => LoadModule access_compat_module
# LoadModule rewrite_module => LoadModule rewrite_module
# ServerName www.*** => ServerName www.*** 

https://github.com/xpf0000/FlyEnv/releases/tag/v4.13.4

The update works wonderfully. Congratulations on the excellent work. One question: Is there a specific reason why it's not possible to install other versions of Apache, only 2.4.66, while other web servers allow the installation of more than one version?

[xpf0000]

The Apache version was obtained from https://www.apachelounge.com/download/. This page only provides a single version, and I couldn't find where the historical versions are located. If you know where to find and download older versions of Apache, please let me know. I can optimize it later to support downloading multiple Apache versions.