You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
icingacli setup config webserver --fpm-uri outputs wrong config when using socks
To Reproduce
icingacli help setup config webserver apache --enable-fpm --fpm-uri=/run/php/php8.3-fpm.sock
Expected behavior
SetHandler "proxy:unix:/run/php/php8.3-fpm.sock|fcgi://localhost/"
instead of
SetHandler "proxy:fcgi:///run/php/php8.3-fpm.sock"
It could be easier to have a --fpm-url (why URI, anyway?) and --fpm-sock-path mutually exclusive options to avoid confusion.
Your Environment
Include as many relevant details about the environment you experienced the problem in
Icinga Web 2 2.12.1
PHP Version 8.3.6
MODULE VERSION
setup 2.12.1
director 1.10.2
graphite 1.2.2
incubator 0.20.0
reactbundle 0.9.0
Server operating system and version:
Distributor ID: Ubuntu
Description: Ubuntu 24.04 LTS
Release: 24.04
Codename: noble
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
icingacli setup config webserver --fpm-uri outputs wrong config when using socks
To Reproduce
icingacli help setup config webserver apache --enable-fpm --fpm-uri=/run/php/php8.3-fpm.sock
Expected behavior
SetHandler "proxy:unix:/run/php/php8.3-fpm.sock|fcgi://localhost/"
instead of
SetHandler "proxy:fcgi:///run/php/php8.3-fpm.sock"
It could be easier to have a --fpm-url (why URI, anyway?) and --fpm-sock-path mutually exclusive options to avoid confusion.
Your Environment
Include as many relevant details about the environment you experienced the problem in
Icinga Web 2 2.12.1
PHP Version 8.3.6
MODULE VERSION
setup 2.12.1
director 1.10.2
graphite 1.2.2
incubator 0.20.0
reactbundle 0.9.0
Distributor ID: Ubuntu
Description: Ubuntu 24.04 LTS
Release: 24.04
Codename: noble
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: