|
From: Sophie <so...@kl...> - 2023-06-18 17:13:37
|
>> Hi everybody,
>>
>> I had a working postfixadmin v 3.1 (sqlite3,nginx) installation until
>> I upgraded from Debian 11 to 12 and along with this php 7.4 to php
>> 8.2.
>>
>> Afterwards, I got a blank screen when hitting the postfixadmin
>> login.php.
>>
>> The error is:
>> 2023/06/12 18:51:11 [error] 3799#3799: *1 FastCGI sent in stderr: "PHP
>> message: PHP Fatal error: Array and string offset access syntax with
>> curly braces is no longer supported in
>> /var/www/mx989.example.int/functions.inc.php on line 697" while
>> reading response header from upstream, client: 12.24.32.82, server:
>> mx989.example.int, request: "GET /login.php HTTP/2.0", upstream:
>> "fastcgi://unix:/run/php/php8.2-fpm.sock:", host: "mx989.example.int"
>>
>> for ($i = 0; $i < $j; ++$i) {
>> switch ($string{$i}) {
>> case '=':
>> case '<':
>> case '>':
>> case ',':
>> case '?':
>> case '_':
>> if ($iEncStart === false) {
>> $iEncStart = $i;
>>
>> I could just upgrade from 3.1 to 3.3.13, but I don't know if this
>> would mend the problem. Potentially it could if brackets are out of
>> fashion :-0
>>
>> Thx,
>> So.
>
> Hi,
>
> Upgrading to 3.3.10 made no difference.
>
> How could i troubleshoot this?
Oddly I am getting a 403 from
error.log:2023/06/18 17:03:57 [error] 105214#105214: *36
"/var/www/a.b.uk/index.php" is forbidden (13: Permission denied)
_# cat index.html_
_<html>_
_<head>_
_ <title>Postfix Admin</title>_
_</head>_
_<body>_
_ <p>The Postfix Admin directory layout changed.</p>_
_ <p>Please update your webserver config so that the DocumentRoot or
Alias points to the directory "public".</p>_
_</body>_
_</html>_
The nginx has:
_server {_
_ listen 443 ssl http2 default deferred;_
_ #listen [::]:443 ipv6only=off ssl;_
_ server_name a.b.uk;_
_ root /var/www/a.b.uk;_
_ index index.php;_
_ charset utf-8;_
Which used to work until I moved from php 7.4 to 8.2.
I changed this to _root /var/www/a.b.uk/public;_ as stated in the
PostfixAdmin index.php, but it did not work. Still got a 403. The curly
bracket error messages seem to have gone after the 3.3.10 upgrade. |
