https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39305
--- Comment #28 from Saiful Amin <[email protected]> --- I spent some time investigating this issue and here's what I found. When you run: `koha-plack --start <instance>` it only starts the Plack (Starman) process for that instance. It does NOT switch Apache from CGI to Plack. Apache will continue using CGI unless explicitly configured otherwise. The switch between CGI and Plack in Apache is controlled by this command: `koha-plack --enable <instance>` This command modifies the Apache configuration for that Koha instance, ensuring these lines are active: For OPAC: Include /etc/koha/apache-shared-opac-plack.conf For Intranet: Include /etc/koha/apache-shared-intranet-plack.conf When you run: `koha-plack --disable <instance>` those Include lines are disabled again, causing Apache to fall back to CGI. I tested this behavior on multiple Koha versions and the behavior was consistent. In my case, the issue was related to SSL, i.e, Let's Encrypt creating another copy of VirtualHost configuration, in which the `koha-plack --enable` had no effect. The fix was to manually update the SSL VirtualHost configuration. If anyone is still experiencing this issue after running: koha-plack --enable <instance> systemctl reload apache2 then it's worth checking: 1. Whether both port 80 and 443 VirtualHosts contain the Plack include lines 2. Whether Apache was reloaded successfully 3. Whether the Plack process is actually running (`koha-plack --status <instance>`) If all of the above are correct and it still serves CGI, then it is worth filing a bug report for that specific Koha version. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
