ISPConfig 3 issueshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues2021-05-21T12:35:34Zhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6126Add mail_plugins to separate dovecot config file which is included earlier2021-05-21T12:35:34ZThomAdd mail_plugins to separate dovecot config file which is included earlierUpdate: mail_plugins (and postmaster address?) are refered to in the service blocks from the ISPConfig template. A script should grab them from the conf-custom file, comment them out in the `99-ispconfig-custom-config.conf` file and add ...Update: mail_plugins (and postmaster address?) are refered to in the service blocks from the ISPConfig template. A script should grab them from the conf-custom file, comment them out in the `99-ispconfig-custom-config.conf` file and add them to a new file `98-ispconfig-custom-config.conf` or something like that. This file should be included in the ISPConfig template before the service blocks.
~~I am now looking to the code of !1459 - This will break the implementation~~
~~Because it is included earlier, values after it will override the custom config, but the custom config should override the config in dovecot.conf ofcourse.
I tested the order before the original MR.~~
~~$mail_plugins should be added, that's good!~~https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6104Creating DNS secondary zone fails if name has ÅÄÖ characters and name without...2022-06-17T12:51:22ZTapio LehtonenCreating DNS secondary zone fails if name has ÅÄÖ characters and name without umlauts exists## short description
Trying to create DNS secondary zone for a zone where zone name has non ASCII characters fails. Looks like if there is zone name with Ö replaced by O or Ä replaced by A adding fails with error
There is already a reco...## short description
Trying to create DNS secondary zone for a zone where zone name has non ASCII characters fails. Looks like if there is zone name with Ö replaced by O or Ä replaced by A adding fails with error
There is already a record for this zone.
## correct behaviour
It should work so also those zones get secondary.
Example: I have primary zone hääyöaie.fi. Adding secondary for that works.
I remove the secondary zone, create new primary zone haayoaie.fi, create secondary zone fo haayoaie.fi. Now creating secondary zone for hääyöaie.fi fails with error "There is already a record for this zone."
How to work around the bug: Create the secondary zone where name has ÅÄÖ characters first. Then adding secondary zone with umlauts removed works.
I'm guessing ISPConfig checks for existing secondary zone by removing umlauts. It does not add umlauts when checking so changing order of creating secondary zones helps
## environment
root@posti:~# cat /etc/debian_version
10.8
ISPConfig 3.2.2
If it might be related to the problem
```
insert the output of `nginx -v` or `apachectl -v` here
root@posti:~# apachectl -v
Server version: Apache/2.4.38 (Debian)
Server built: 2020-08-25T20:08:29
```
```
insert the output of `php -v` here
root@posti:~# php -v
PHP 7.3.27-9+0~20210227.82+debian10~1.gbpa4a3d6 (cli) (built: Feb 27 2021 15:50:50) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.27, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.27-9+0~20210227.82+debian10~1.gbpa4a3d6, Copyright (c) 1999-2018, by Zend Technologies
root@posti:~#
```https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6087Apache vhost config invalid when using redirect: proxy and to-https2022-06-17T11:16:13ZPetr MifekApache vhost config invalid when using redirect: proxy and to-https## short description
Using both Redirect Type: proxy and Rewrite HTTP to HTTPS with Apache results in invalid configuration - Apache returns status 500. Site is configured on server with Apache and SSL with Letsencrypt enabled.
## corre...## short description
Using both Redirect Type: proxy and Rewrite HTTP to HTTPS with Apache results in invalid configuration - Apache returns status 500. Site is configured on server with Apache and SSL with Letsencrypt enabled.
## correct behaviour
The request should be handled with a rewrite to HTTPS and then proxied.
```
# Generated (faulting) config snippet (Apache non-ssl part of the config):
RewriteEngine on
RewriteCond %{REQUEST_URI} ^/\.well-known/acme-challenge/
RewriteRule ^ - [END]
RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
RewriteRule ^/(.*)$ http://1.2.3.4/$1 [proxy]
RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]
RewriteRule ^/(.*)$ http://1.2.3.4/$1 [proxy]
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L,NE]
```
```
# Updated (working) config snippet (Apache non-ssl part of the config):
RewriteEngine on
RewriteCond %{REQUEST_URI} ^/\.well-known/acme-challenge/
RewriteRule ^ - [END]
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L,NE]
RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
RewriteRule ^/(.*)$ http://1.2.3.4/$1 [proxy]
RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]
RewriteRule ^/(.*)$ http://1.2.3.4/$1 [proxy]
```
## environment
Server OS: debian
Server OS version: buster
ISPConfig version: 3.2.2/nightly
## proposed fix
Move the HTTP-to-HTTPS rewrite up just after the acme challenge exemption:
Patch:
```
--- ispconfig/server/conf/vhost.conf.master 2021-03-04 01:17:38.371357346 +0000
+++ ispconfig/server/conf/vhost.conf.master.fix_tossl_and_proxy 2021-03-04 01:16:47.113325799 +0000
@@ -493,6 +493,15 @@
RewriteCond %{REQUEST_URI} ^/\.well-known/acme-challenge/
RewriteRule ^ - [END]
</tmpl_if>
+<tmpl_if name='ssl_enabled'>
+<tmpl_else>
+<tmpl_if name='rewrite_to_https' op='==' value='y'>
+ RewriteCond %{HTTPS} off
+ <tmpl_if name='apache_version' op='<' value='2.4' format='version'>RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/
+</tmpl_if>
+ RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L,NE]
+</tmpl_if>
+</tmpl_if>
<tmpl_if name='seo_redirect_enabled'>
RewriteCond %{HTTP_HOST} <tmpl_var name='seo_redirect_operator'>^<tmpl_var name='seo_redirect_origin_domain'>$ [NC]
<tmpl_if name='apache_version' op='<' value='2.4' format='version'>
@@ -521,15 +530,6 @@
RewriteRule ^/(.*)$ <tmpl_var name='rewrite_target'><tmpl_if name="rewrite_add_path" op="==" value="y">$1</tmpl_if> <tmpl_var name='rewrite_type'>
</tmpl_loop>
-<tmpl_if name='ssl_enabled'>
-<tmpl_else>
-<tmpl_if name='rewrite_to_https' op='==' value='y'>
- RewriteCond %{HTTPS} off
- <tmpl_if name='apache_version' op='<' value='2.4' format='version'>RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/
-</tmpl_if>
- RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L,NE]
-</tmpl_if>
-</tmpl_if>
</tmpl_if>
# add support for apache mpm_itk
```
## screenshots
![ApacheRedirProxyAndHttpsResultsInStatus500](/uploads/578e36743df07352654ae7c2d349250c/ApacheRedirProxyAndHttpsResultsInStatus500.jpg)https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6079Mailboxpassword Encoding not correct2023-08-08T07:21:26ZDominikMailboxpassword Encoding not correct## short description
Setting Mailboxpasswords with some special chars (like e.g. §) doesn't work on Ubuntu/MariaDB. Password is set, but Login isn't possible with web-clients like roundcube - i already discussed this with Florian, but al...## short description
Setting Mailboxpasswords with some special chars (like e.g. §) doesn't work on Ubuntu/MariaDB. Password is set, but Login isn't possible with web-clients like roundcube - i already discussed this with Florian, but also after that, I don't come to a solution or the real reason, why it is, like it is... So maybe somebody out there has the same issue with this setup and might have an idea.
## environment
Server OS: Ubuntu 20.04
ISPConfig version: 3.2.2 (also seen with 3.1.x)
If I change the following in /interface/lib/classes/auth.inc.php, Line 272
```
public function crypt_password($cleartext_password, $charset = 'UTF-8') {
if($charset != 'UTF-8') {
//$cleartext_password = mb_convert_encoding($cleartext_password, $charset, 'UTF-8');
}
```
this means removing the mb_convert_encoding
everything works fine!!
additionally if I add this:
```
public function crypt_password($cleartext_password, $charset = 'UTF-8') {
if(($charset != 'UTF-8') && (mb_detect_encoding($cleartext_password) != 'UTF-8)) {
$cleartext_password = mb_convert_encoding($cleartext_password, $charset, 'UTF-8');
}
```
it also works fine!!
this means in my setup encoding IS already UTF-8, and doesn't need a second encoding...
But I don't know, if this is the solution - since the function is explicitly called with parameter $charset='ISO-8859-1'
this happens in file
/interface/lib/classes/tform_base.inc.php
in Line 1373
and I don't understand the Comment that was added there:
```
} elseif(isset($field['encryption']) && $field['encryption'] == 'CRYPTMAIL') {
// The password for the mail system needs to be converted to latin1 before it is hashed.
$record[$key] = $app->auth->crypt_password(stripslashes($record[$key]),'ISO-8859-1');
$sql_insert_val .= "'".$app->db->quote($record[$key])."', ";
}
```
so it seems like: nobody looks on the real encoding of the incoming password, but it is "simulated" to ISO-8859-1 and as a consequence it is encoed....
## proposed fix
change this line:
/interface/lib/classes/tform_base.inc.php - Line 1373
```
$entry = stripslashes($record[$key]);
$record[$key] = $app->auth->crypt_password($entry,mb_detect_encoding($entry));
```
## additional comment
What I found to my astonishment
The Problem with wrong encoded password doesn't seem to be a problem for Mailclient Thunderbird. If you access such a double encoded password-mailbox with Thunderbird you find a password-missmatch log-entry in postfix-log, but Thunderbird seems to retry and change some things and always (reproducible) in the third try, Thunderbird can access... But Roundcube for example only tries once and cannot access....
If i change the things above, in both cases login works on the first try...3.2.12https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6078Default server PHP handler used even if client does not have the handler in h...2021-03-01T12:04:34ZThomDefault server PHP handler used even if client does not have the handler in his limitsIf the server's default is FastCGI (or any other mode), and the client creates a web, the default PHP handler is set, even if it is not within the client's limits.If the server's default is FastCGI (or any other mode), and the client creates a web, the default PHP handler is set, even if it is not within the client's limits.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6025adding dns zone should add DKIM records2021-01-22T07:21:01ZJesse Norelladding dns zone should add DKIM recordsWhen adding a DNS zone, if a corresponding mail zone exists with a DKIM record set, that DKIM record should be added to DNS records. (Applies both to the dns wizard and adding a zone manually.)
Background:
Having found that many of our...When adding a DNS zone, if a corresponding mail zone exists with a DKIM record set, that DKIM record should be added to DNS records. (Applies both to the dns wizard and adding a zone manually.)
Background:
Having found that many of our DNS zones to not have DKIM records even though they are configured in the Email domain, the likely reason is the order of adding them - if you add an Email domain first, including a DKIM records, and add the DNS zone second, you will not have any DKIM record created in DNS. Mail will still be signed with the DKIM key, just not verifiable.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6024change shell user Base Dir creates warning2022-09-25T19:19:23ZJesse Norellchange shell user Base Dir creates warningWhen changing the shell user Base dir, in my case from /var/www/clients/client1/web20 to /var/www/clients/client1/web20/blah, I see this error:
```
21.01.2021-13:08 - DEBUG - Calling function 'update' from plugin 'shelluser_base_plugin' ...When changing the shell user Base dir, in my case from /var/www/clients/client1/web20 to /var/www/clients/client1/web20/blah, I see this error:
```
21.01.2021-13:08 - DEBUG - Calling function 'update' from plugin 'shelluser_base_plugin' raised by event 'shell_user_update'.
21.01.2021-13:08 - DEBUG - Homedir New: /var/www/clients/client1/web20/blah
21.01.2021-13:08 - DEBUG - Homedir Old: /var/www/clients/client1/web20
21.01.2021-13:08 - DEBUG - safe_exec cmd: chattr -i '/var/www/clients/client1/web20' - return code: 0
PHP Warning: rename(/var/www/clients/client1/web20,/var/www/clients/client1/web20/blah): Invalid argument in /usr/local/ispconfig/server/lib/classes/
system.inc.php on line 894
```
(From https://www.howtoforge.com/community/threads/the-following-changes-are-not-yet-populated-to-all-servers.86171/#post-416503)Jesse NorellJesse Norellhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6004private/quota-status is dovecot-only2022-03-01T21:36:41ZJesse Norellprivate/quota-status is dovecot-onlyThe private/quota-status service is always configured (in smtpd_recipient_restrictions), need to remove that if using courier.
https://www.howtoforge.com/community/threads/ispconfig-3-2-with-courier-incoming-mails-are-undelivered.86045/The private/quota-status service is always configured (in smtpd_recipient_restrictions), need to remove that if using courier.
https://www.howtoforge.com/community/threads/ispconfig-3-2-with-courier-incoming-mails-are-undelivered.86045/https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5979symlinked pure-ftpd.pem to ispserver.pem not chmod 6002021-03-09T01:29:22ZHj Ahmad Rasyid Hj Ismailsymlinked pure-ftpd.pem to ispserver.pem not chmod 600I finally upgraded Ubuntu 18.04 to 20.04 (nginx) and everything when smooth EXCEPT:
pureftpd-pem that is symlinked to ispserver.pem is not defaulted to 600, as ispserver.pem, as it should be, resulting services relying on it failed.
Th...I finally upgraded Ubuntu 18.04 to 20.04 (nginx) and everything when smooth EXCEPT:
pureftpd-pem that is symlinked to ispserver.pem is not defaulted to 600, as ispserver.pem, as it should be, resulting services relying on it failed.
This is also reported in the forum by someone else: https://www.howtoforge.com/community/threads/monit-and-ispconfig3-2.85509
I am making a MR for it at https://git.ispconfig.org/ispconfig/ispconfig3/-/merge_requests/1370 anyway, and open it for further discussions.
Edited and added: Upon auto renewal of LE SSL certs for the server, ispserver.pem regenerated but the permission is not changed to 600. So the issue persisted unless resolved but the issue may not be on ISPConfig installer / updater.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5953Reverse proxy Lets Encrypt Acme snippet2023-09-28T20:33:47ZXaver MaierhoferReverse proxy Lets Encrypt Acme snippet## short description
If Redirect Type proxy is used lets encrypt fail won't work.
The vhost has no acme part.
(No custom templates in use)
## correct behaviour
Add the snippet if lets encrypt is enabled.
## environment
Server OS: debi...## short description
If Redirect Type proxy is used lets encrypt fail won't work.
The vhost has no acme part.
(No custom templates in use)
## correct behaviour
Add the snippet if lets encrypt is enabled.
## environment
Server OS: debian
Server OS version: 10
ISPConfig version: 3.2.1
Webserver: nginx3.2.12https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5946backup unmount script errors on mail server2020-12-04T13:52:26ZJesse Norellbackup unmount script errors on mail serverRecent 3.2 backup changes cause errors about unmount scripts failing.
Some discussion/info in https://www.howtoforge.com/community/threads/backup-directory-var-backup-could-not-be-unmounted.85701/
I see this error email from our mail s...Recent 3.2 backup changes cause errors about unmount scripts failing.
Some discussion/info in https://www.howtoforge.com/community/threads/backup-directory-var-backup-could-not-be-unmounted.85701/
I see this error email from our mail server node every night. The above discussion seems to be involving mail servers as well. I believe I do not see this error from our web/db server node (which uses the same mount/unmount scripts, to shared storage).https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/59413.2.1 update configured postfix on non-mail node2021-03-23T16:53:53ZJesse Norell3.2.1 update configured postfix on non-mail nodeOn a nameserver-only node, postfix is installed for local use, but was configured by the installer during a 3.1->3.2.1 update (so mail is now broken, with no amavis, etc.).
This was a debian 9 box. A second nameserver (mirror of the fi...On a nameserver-only node, postfix is installed for local use, but was configured by the installer during a 3.1->3.2.1 update (so mail is now broken, with no amavis, etc.).
This was a debian 9 box. A second nameserver (mirror of the first one) has been updated to debian 10 and did not have this problem (postfix is installed there, too).https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5895"PHP Version is invalid" When hiding default php version2020-11-19T09:41:42ZPascal Dreissen"PHP Version is invalid" When hiding default php versionWhen you select in System -> Server config -> <server> -> Web -> PHP Settings = Hide Default PHP-Version in selectbox. Selecting Mod_PHP in a site config you cannot save and ISPConfig states: "PHP Version is invalid."
When you deselect ...When you select in System -> Server config -> <server> -> Web -> PHP Settings = Hide Default PHP-Version in selectbox. Selecting Mod_PHP in a site config you cannot save and ISPConfig states: "PHP Version is invalid."
When you deselect the hide default option you can select Mod_PHP and save again.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5888Wildcard (*) not allowed in SPF record editor2020-12-21T17:37:37ZThomWildcard (*) not allowed in SPF record editorShould be allowed because we introduced a function for thisShould be allowed because we introduced a function for thishttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5881Translating the monitor language file damages the Monitor section2020-11-03T16:04:29ZClemente NogueiraTranslating the monitor language file damages the Monitor sectionI have been translating the ISPConfig 3.2 language into pt-pt.
When I translated the "monitor pt.lng" file and tried to open the Monitor tab, it blocked and did not open.
When I repaired the file for the English equivalent, everything ...I have been translating the ISPConfig 3.2 language into pt-pt.
When I translated the "monitor pt.lng" file and tried to open the Monitor tab, it blocked and did not open.
When I repaired the file for the English equivalent, everything went back to normal.
Also, the problem only happens when I use the pt-pt language into which I translated the file. If I choose the English language everything goes back to normal.
It seems that the problem stems from the translation.
I repeated the procedure several times, it always happens.
I checked the permissions and everything is normal: 770 ispconfig/ispconfig
I checked the file information, and found out when it was saved the quotes ' are replaced by ".
$ wb ['Server Load'] = 'Servidor carregado';
per
$ wb ['Server Load'] = "Servidor carregado";https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5876Error on sites_web_vhost_subdomain_add2022-02-26T20:55:49ZLucaError on sites_web_vhost_subdomain_addDear,
i have tried to fork the project to my user in order to propose a merge about this fix, but can't do it (seems that i have no permission to create a project).
By the way, on that method lib/classes/remote.d/sites.inc.php:sites_we...Dear,
i have tried to fork the project to my user in order to propose a merge about this fix, but can't do it (seems that i have no permission to create a project).
By the way, on that method lib/classes/remote.d/sites.inc.php:sites_web_vhost_subdomain_add this line
`if($params['document_root'] == '') $params['document_root'] = '-';`
should be instead return an error if document_root is empty. Otherwise the sites_web_vhost_subdomain_add does not work at all.
tyhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5874.htaccess not updated in client change2020-11-01T16:17:38ZTony G.htaccess not updated in client changeChange the client for a site and all folders correctly move to the new clientX/webY location. But in a protected folder the .htaccess file has the original path to the AuthUserFile.Change the client for a site and all folders correctly move to the new clientX/webY location. But in a protected folder the .htaccess file has the original path to the AuthUserFile.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5861PHP version list does not load when opening the form to create a new Subdomai...2020-10-24T10:38:48ZDiogo BragaPHP version list does not load when opening the form to create a new Subdomain/Aliasdomain VhostFix suggestion:
On the template sites/templates/web_vhost_domain_edit.htm, change the following lines:
```
jQuery('#parent_domain_id').change(function() {
reloadServerId(false);
});
// new Vhostsubdomains/Vhostaliasdomains
if(serv...Fix suggestion:
On the template sites/templates/web_vhost_domain_edit.htm, change the following lines:
```
jQuery('#parent_domain_id').change(function() {
reloadServerId(false);
});
// new Vhostsubdomains/Vhostaliasdomains
if(serverId == ''){
jQuery('#parent_domain_id').trigger('change');
}
```
to
```
jQuery('#parent_domain_id').change(function(e, noFormChange) {
reloadServerId(noFormChange);
});
// new Vhostsubdomains/Vhostaliasdomains
if(serverId == ''){
jQuery('#parent_domain_id').trigger('change', [true]);
}
```https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5857jailkit_chroot_authorized_keys_template in shelluser_base_plugin.inc.php2020-10-26T10:01:53ZJesse Norelljailkit_chroot_authorized_keys_template in shelluser_base_plugin.inc.phpThere are two `shelluser_*_plugin.inc.php` files, `shelluser_jailkit_plugin.inc.php` was updated to use the `jailkit_chroot_authorized_keys_template` server config setting, but `shelluser_base_plugin.inc.php` still has `/root/.ssh/author...There are two `shelluser_*_plugin.inc.php` files, `shelluser_jailkit_plugin.inc.php` was updated to use the `jailkit_chroot_authorized_keys_template` server config setting, but `shelluser_base_plugin.inc.php` still has `/root/.ssh/authorized_keys` hardcoded. I have not explored the conditions under which the latter is effective (I'd guess creating a shell user which is not using jailkit?).https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5835Backup tries to also run -and fails- on secondary DNS server, without having ...2020-10-21T08:54:08ZFerenc CsizmadiaBackup tries to also run -and fails- on secondary DNS server, without having Webservice enabled here.## short description
What is happening and what is wrong with that?
I have a multi-server environment with 2 servers (one of them is the master) and a secondary DNS server that has only DB and DNS services installed and enabled on. The ...## short description
What is happening and what is wrong with that?
I have a multi-server environment with 2 servers (one of them is the master) and a secondary DNS server that has only DB and DNS services installed and enabled on. The secondary DNS server is mirroring the "master" webserver where the primary DNS service runs.
Since the 3.2 update the backup of the websites is reporting error on the secondary DNS server as well, despite the fact these websites are not residing on it but on the master webserver only. The errors stating that the backup was not possible to run for the sites. (since the path is not valid on the secondary DNS but only on the master web server.)
The backup on the server, holding the site takes place properly.
## correct behaviour
What should happen instead?
The backup shall only run on the webserver where the sites do reside and not on any mirrored server, especially if the
service is not enabled on it at all.
## environment
Server OS: debian 9
Server OS version: stretch
ISPConfig version: 3.2
_you can use `grep 'ISPC_APP_VERSION' /usr/local/ispconfig/server/lib/config.inc.php` to get it from the command line_
If it might be related to the problem
```
insert the output of `nginx -v` or `apachectl -v` here
root@castor:~# apachectl -v
Server version: Apache/2.4.25 (Debian)
Server built: 2019-10-13T15:43:54
insert the output of `php -v` here
root@castor:~# php -v
PHP 7.0.33-34+0~20201018.42+debian9~1.gbp80c9be (cli) (built: Oct 18 2020 21:35:49) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies
with Zend OPcache v7.0.33-34+0~20201018.42+debian9~1.gbp80c9be, Copyright (c) 1999-2017, by Zend Technologies
with Xdebug v2.8.1, Copyright (c) 2002-2019, by Derick Rethans
## proposed fix
optional, of course.
if you want to post code snippets, please use
```
your code
```
or attach a code file. Best is to create a merge request of course.
## references
if you know of related bugs or feature requests, please reference them by using `#<bugnumber>`, e. g. #123
if you have done a merge request already, please reference it by using `!<mergenumber>`, e. g. !12
if you know of a forum post on howtoforge.com that deals with this topic, just add the link to the forum topic here
## screenshots
optional, of course.
Add screenshots of the problem by clicking "Attach a file" on the bottom right.
## log entries
```
apache / nginx error.log lines (if related)
```