ISPConfig 3 issueshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues2019-07-03T10:58:32Zhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5070Firewall > Character not allowed in tcp port definition2019-07-03T10:58:32ZAndreas B.Firewall > Character not allowed in tcp port definition## short description
What is happening and what is wrong with that?
Firewall Open TCP ports limit to 255 chars
## correct behaviour
What should happen instead?
`error message : "Character not allowed in tcp port definition. Allowed cha...## short description
What is happening and what is wrong with that?
Firewall Open TCP ports limit to 255 chars
## correct behaviour
What should happen instead?
`error message : "Character not allowed in tcp port definition. Allowed characters are numbers, ":" and ","."`
## environment
Server OS: Debian
Server OS version: jessie 8.11
ISPConfig version: 3.1.12 (define('ISPC_APP_VERSION', '3.1.12');)
If it might be related to the problem
no more output.
## references
https://www.howtoforge.de/forum/threads/firewall-character-not-allowed-in-tcp-port-definition.11141/#post-55559
## screenshots
![2018-07-03_15_55_14-ISPConfig](/uploads/bb16d9b46431b5ec4f03a0cf0a226de2/2018-07-03_15_55_14-ISPConfig.png)
## log entries
no entries3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5293If an email is submitted via SMTPUTF8 it will bounce2019-07-03T10:31:34ZPatrick GatterdamIf an email is submitted via SMTPUTF8 it will bounce## short description
If a email is accepted via SMTPUTF8 and amavis via port 10026 is used the email is bounced.
I think this happens if the mail is being forwarded.
## correct behaviour
amavis should announce SMTPUTF8 on port 10026 cor...## short description
If a email is accepted via SMTPUTF8 and amavis via port 10026 is used the email is bounced.
I think this happens if the mail is being forwarded.
## correct behaviour
amavis should announce SMTPUTF8 on port 10026 correctly, port 10024 is not affected
## environment
Server OS: (debian)
Server OS version: (stretch)
ISPConfig version: (3.1.13p1)
## proposed fix
remove this line from install/tpl/amavisd_user_config.master
```
smtpd_discard_ehlo_keywords => ['8BITMIME'],
```
## references
http://www.postfix.org/SMTPUTF8_README.html
```
Introduced with Postfix version 3.0, this fully supports UTF-8 email addresses and UTF-8 message header values.
```
https://www.ijs.si/software/amavisd/release-notes.txt
```
A SMTP response to an EHLO command will now announce SMTPUTF8 capability by default.
```
## log entries
```
relay=127.0.0.1[127.0.0.1]:10026, delay=0.2, delays=0.15/0/0.05/0, dsn=5.6.7, status=bounced (SMTPUTF8 is required, but was not offered by host 127.0.0.1[127.0.0.1])
```3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5303Database Backup including routines2019-07-03T10:29:25ZThomasDatabase Backup including routines## short description
Is it a bad pratice to include procedures and functions in dump ?
If not, would be nice.
## proposed fix
`mysqldump --routines`
in ispconfig/server/lib/classes/cron.d/500-backup.inc.php## short description
Is it a bad pratice to include procedures and functions in dump ?
If not, would be nice.
## proposed fix
`mysqldump --routines`
in ispconfig/server/lib/classes/cron.d/500-backup.inc.php3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5309Debian testing/unknown template is outdated2019-07-03T10:03:19ZĆukasz DomeradzkiDebian testing/unknown template is outdatedHello.
I have two issues with current installation/update process. In particular, settings for Debian Testing no longer apply to that version (for example, older php version), and I also believe that unknown Debian version should point ...Hello.
I have two issues with current installation/update process. In particular, settings for Debian Testing no longer apply to that version (for example, older php version), and I also believe that unknown Debian version should point to Testing, which is the most correct in terms of future compatibility. For example, my existing setup is detected as such, because I'm using Testing and not Sid.
I've attached my patch below that addresses above issues. I'm not sending PR with it right away as I'm not sure if you're fine with my approach. Please review it and if you could do something similar (or just merging my patch) to address my issue above, I'd appreciate that.
```diff
--- ispconfig3_install/install/dist/conf/debiantesting.conf.php 2018-08-17 18:22:58.000000000 +0200
+++ ispconfig3_install2/install/dist/conf/debiantesting.conf.php 2019-05-20 13:17:47.644034627 +0200
@@ -1,7 +1,7 @@
<?php
/*
-Copyright (c) 2016, Till Brehm, ISPConfig UG
+Copyright (c) 2017, Till Brehm, ISPConfig UG
All rights reserved.
Redistribution and use in source and binary forms, with or without modification,
@@ -28,11 +28,11 @@ NEGLIGENCE OR OTHERWISE) ARISING IN ANY
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/
-//*** Ubuntu 16.04 default settings
+//*** Ubuntu 18.04 default settings
//* Main
$conf['language'] = 'en';
-$conf['distname'] = 'ubuntu1604';
+$conf['distname'] = 'ubuntu1804';
$conf['hostname'] = 'server1.domain.tld'; // Full hostname
$conf['ispconfig_install_dir'] = '/usr/local/ispconfig';
$conf['ispconfig_config_dir'] = '/usr/local/ispconfig';
@@ -83,8 +83,8 @@ $conf['apache']['version'] = '2.4';
$conf['apache']['vhost_conf_dir'] = '/etc/apache2/sites-available';
$conf['apache']['vhost_conf_enabled_dir'] = '/etc/apache2/sites-enabled';
$conf['apache']['vhost_port'] = '8080';
-$conf['apache']['php_ini_path_apache'] = '/etc/php/7.0/apache2/php.ini';
-$conf['apache']['php_ini_path_cgi'] = '/etc/php/7.0/cgi/php.ini';
+$conf['apache']['php_ini_path_apache'] = '/etc/php/7.3/apache2/php.ini';
+$conf['apache']['php_ini_path_cgi'] = '/etc/php/7.3/cgi/php.ini';
//* Website base settings
$conf['web']['website_basedir'] = '/var/www';
@@ -99,7 +99,7 @@ $conf['web']['apps_vhost_user'] = 'ispap
$conf['web']['apps_vhost_group'] = 'ispapps';
//* Fastcgi
-$conf['fastcgi']['fastcgi_phpini_path'] = '/etc/php/7.0/cgi/';
+$conf['fastcgi']['fastcgi_phpini_path'] = '/etc/php/7.3/cgi/';
$conf['fastcgi']['fastcgi_starter_path'] = '/var/www/php-fcgi-scripts/[system_user]/';
$conf['fastcgi']['fastcgi_bin'] = '/usr/bin/php-cgi';
@@ -183,7 +183,7 @@ $conf['jailkit']['installed'] = false; /
$conf['jailkit']['config_dir'] = '/etc/jailkit';
$conf['jailkit']['jk_init'] = 'jk_init.ini';
$conf['jailkit']['jk_chrootsh'] = 'jk_chrootsh.ini';
-$conf['jailkit']['jailkit_chroot_app_programs'] = '/usr/bin/groups /usr/bin/id /usr/bin/dircolors /usr/bin/lesspipe /usr/bin/basename /usr/bin/dirname /usr/bin/nano /usr/bin/pico /usr/bin/mysql /usr/bin/mysqldump /usr/bin/git /usr/bin/git-receive-pack /usr/bin/git-upload-pack /usr/bin/unzip /usr/bin/zip /bin/tar /bin/rm /usr/bin/patch';
+$conf['jailkit']['jailkit_chroot_app_programs'] = '/usr/bin/groups /usr/bin/id /usr/bin/dircolors /usr/bin/lesspipe /usr/bin/basename /usr/bin/dirname /usr/bin/nano /usr/bin/pico /usr/bin/mysql /usr/bin/mysqldump /usr/bin/git /usr/bin/git-receive-pack /usr/bin/git-upload-pack /usr/bin/unzip /usr/bin/zip /bin/tar /bin/rm /usr/bin/patch /etc/localtime';
$conf['jailkit']['jailkit_chroot_cron_programs'] = '/usr/bin/php /usr/bin/perl /usr/share/perl /usr/share/php';
//* Squid
@@ -201,11 +201,11 @@ $conf['nginx']['vhost_conf_enabled_dir']
$conf['nginx']['init_script'] = 'nginx';
$conf['nginx']['vhost_port'] = '8080';
$conf['nginx']['cgi_socket'] = '/var/run/fcgiwrap.socket';
-$conf['nginx']['php_fpm_init_script'] = 'php7.0-fpm';
-$conf['nginx']['php_fpm_ini_path'] = '/etc/php/7.0/fpm/php.ini';
-$conf['nginx']['php_fpm_pool_dir'] = '/etc/php/7.0/fpm/pool.d';
+$conf['nginx']['php_fpm_init_script'] = 'php7.3-fpm';
+$conf['nginx']['php_fpm_ini_path'] = '/etc/php/7.3/fpm/php.ini';
+$conf['nginx']['php_fpm_pool_dir'] = '/etc/php/7.3/fpm/pool.d';
$conf['nginx']['php_fpm_start_port'] = 9010;
-$conf['nginx']['php_fpm_socket_dir'] = '/var/lib/php7.0-fpm';
+$conf['nginx']['php_fpm_socket_dir'] = '/var/lib/php7.3-fpm';
//* OpenVZ
$conf['openvz']['installed'] = false;
diff -rupN ispconfig3_install/install/lib/install.lib.php ispconfig3_install2/install/lib/install.lib.php
--- ispconfig3_install/install/lib/install.lib.php 2019-02-19 15:31:07.000000000 +0100
+++ ispconfig3_install2/install/lib/install.lib.php 2019-05-20 13:25:25.990839694 +0200
@@ -238,7 +238,7 @@ function get_distname() {
$distname = 'Debian';
$distver = 'Unknown';
$distid = 'debian60';
- $distconfid = 'debian90';
+ $distconfid = 'debiantesting';
$distbaseid = 'debian';
swriteln("Operating System: Debian or compatible, unknown version.\n");
}
```3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5313Extend custom php.ini check regex2019-07-03T10:02:49ZTill BrehmExtend custom php.ini check regexhttps://forum.howtoforge.de/threads/fehler-invalid_custom_php_ini_settings_txt.11654/#post-57922https://forum.howtoforge.de/threads/fehler-invalid_custom_php_ini_settings_txt.11654/#post-579223.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5113PHP error in server config edit form when old PHP versions are used2019-06-26T14:09:13ZTill BrehmPHP error in server config edit form when old PHP versions are usedSee comments in #5063 for details.See comments in #5063 for details.3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5129Syntax errors in PHP 5.3.32019-06-26T14:06:59ZTill BrehmSyntax errors in PHP 5.3.3There are some syntax errors in PHP 5.3.3 due to lack of new PHP array access function syntax:
https://www.howtoforge.com/community/threads/cant-generate-dkim-and-access-server-config.80015/There are some syntax errors in PHP 5.3.3 due to lack of new PHP array access function syntax:
https://www.howtoforge.com/community/threads/cant-generate-dkim-and-access-server-config.80015/3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5033Renewal of letsencrypt does not restart/reload nginx2019-06-26T13:51:42ZRajko AlbrechtRenewal of letsencrypt does not restart/reload nginx## short description
When renew letsencrypt certificates from domains in nginx service the nginx service will not restart in debian9. So it may happen, that a non valid certificate is send by nginx to clients instead of the newly generat...## short description
When renew letsencrypt certificates from domains in nginx service the nginx service will not restart in debian9. So it may happen, that a non valid certificate is send by nginx to clients instead of the newly generated one.
## correct behaviour
After renew of letsencrypt nginx should be restarted. On a debian stretch with apache as webserver it works.
## environment
Server OS: Debian
Server OS version: Stretch
ISPConfig version: 3.1.11
```
nginx version: nginx/1.10.3
```
Not sure, but I think the problem is in `900-letsencrypt.inc.php` in line 71 - `systemctl force-reload nginx` does not work.
I had not tracked down what is realy send at this point but wouldn't be a `restart` better for nginx?
Bye
Rajko3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5326LE Renewal issue on systems that use the relative symlink option for websites2019-06-26T13:48:15ZTill BrehmLE Renewal issue on systems that use the relative symlink option for websitesThere is an issue with LE renewals when the relative symlinks option is on under system > server config > web. This option is off by default and only needed on some specific chrooted apache configurations, not used in any standard ISPCon...There is an issue with LE renewals when the relative symlinks option is on under system > server config > web. This option is off by default and only needed on some specific chrooted apache configurations, not used in any standard ISPConfig setup, so very few users are affected by this.3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5258Let's Encrypt Cert file: does not exist.2019-05-13T16:08:06ZBart DorlandtLet's Encrypt Cert file: does not exist.## short description
While trying to enable a website with a LE certificate, it goes through the process, which all looks fine, except for the part it says: "Let's Encrypt Cert file: does not exist." (with debug enabled).
Therefore not ...## short description
While trying to enable a website with a LE certificate, it goes through the process, which all looks fine, except for the part it says: "Let's Encrypt Cert file: does not exist." (with debug enabled).
Therefore not enabling SSL (with LE) on the website.
Even though the LE certs are created in the correct directory.
## correct behaviour
The letsencrypt log shows the process where the certificate has been received. It is expected that ispconfig uses that certificate to enable the website with SSL.
## environment
Server OS: Debian
Server OS version: 9.7, stretch
ISPConfig version: 3.1.13
## log entries
/var/log/ispconfig/ispconfig.log
```
27.02.2019-13:37 - DEBUG - Calling function 'check_phpini_changes' from plugin 'webserver_plugin' raised by action 'server_plugins_loaded'.
27.02.2019-13:37 - DEBUG - Found 1 changes, starting update process.
27.02.2019-13:37 - DEBUG - Calling function 'ssl' from plugin 'apache2_plugin' raised by event 'web_domain_update'.
27.02.2019-13:37 - DEBUG - Calling function 'update' from plugin 'apache2_plugin' raised by event 'web_domain_update'.
27.02.2019-13:37 - DEBUG - Verified domain zwart-licht.nl should be reachable for letsencrypt.
27.02.2019-13:37 - DEBUG - Verified domain www.zwart-licht.nl should be reachable for letsencrypt.
27.02.2019-13:37 - DEBUG - Create Let's Encrypt SSL Cert for: zwart-licht.nl
27.02.2019-13:37 - DEBUG - Let's Encrypt SSL Cert domains: --domains zwart-licht.nl --domains www.zwart-licht.nl
27.02.2019-13:37 - DEBUG - exec: /opt/eff.org/certbot/venv/bin/certbot certonly -n --text --agree-tos --expand --authenticator webroot --server https://acme-v02.api.letsencrypt.org/directory --rsa-key-size 4096 --email postmaster@zwart-licht.nl --domains zwart-licht.nl --domains www.zwart-licht.nl --webroot-path /usr/local/ispconfig/interface/acme
27.02.2019-13:37 - DEBUG - Let's Encrypt Cert file: does not exist.
27.02.2019-13:37 - DEBUG - Writing the vhost file: /etc/apache2/sites-available/zwart-licht.nl.vhost
27.02.2019-13:37 - DEBUG - Writing the PHP-FPM config file: /etc/php/7.0/fpm/pool.d/web22.conf
27.02.2019-13:37 - DEBUG - Calling function 'restartPHP_FPM' from module 'web_module'.
27.02.2019-13:37 - DEBUG - Restarting php-fpm: systemctl reload php7.0-fpm.service
27.02.2019-13:37 - DEBUG - Apache status is: running
27.02.2019-13:37 - DEBUG - Calling function 'restartHttpd' from module 'web_module'.
27.02.2019-13:37 - DEBUG - Restarting httpd: systemctl restart apache2.service
27.02.2019-13:37 - DEBUG - Apache restart return value is: 0
27.02.2019-13:37 - DEBUG - Apache online status after restart is: running
27.02.2019-13:37 - DEBUG - Processed datalog_id 1344
27.02.2019-13:37 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
```
/var/log/letsencrypt/letsencrypt.log
```
2019-02-27 13:37:12,844:DEBUG:certbot.storage:Archive directory /etc/letsencrypt/archive/zwart-licht.nl and live directory /etc/letsencrypt/live/zwart-licht.nl created.
2019-02-27 13:37:12,844:DEBUG:certbot.storage:Writing certificate to /etc/letsencrypt/live/zwart-licht.nl/cert.pem.
2019-02-27 13:37:12,845:DEBUG:certbot.storage:Writing private key to /etc/letsencrypt/live/zwart-licht.nl/privkey.pem.
2019-02-27 13:37:12,845:DEBUG:certbot.storage:Writing chain to /etc/letsencrypt/live/zwart-licht.nl/chain.pem.
2019-02-27 13:37:12,845:DEBUG:certbot.storage:Writing full chain to /etc/letsencrypt/live/zwart-licht.nl/fullchain.pem.
2019-02-27 13:37:12,845:DEBUG:certbot.storage:Writing README to /etc/letsencrypt/live/zwart-licht.nl/README.
2019-02-27 13:37:12,959:DEBUG:certbot.plugins.selection:Requested authenticator webroot and installer <certbot.cli._Default object at 0x7f846dcbc4d0>
2019-02-27 13:37:13,086:DEBUG:certbot.cli:Var webroot_path=/usr/local/ispconfig/interface/acme (set by user).
2019-02-27 13:37:13,086:DEBUG:certbot.cli:Var webroot_map=set(['webroot_path']) (set by user).
2019-02-27 13:37:13,362:DEBUG:certbot.cli:Var server=https://acme-v02.api.letsencrypt.org/directory (set by user).
2019-02-27 13:37:14,026:DEBUG:certbot.cli:Var webroot_path=/usr/local/ispconfig/interface/acme (set by user).
2019-02-27 13:37:14,145:DEBUG:certbot.cli:Var rsa_key_size=4096 (set by user).
2019-02-27 13:37:14,779:DEBUG:certbot.cli:Var authenticator=webroot (set by user).
2019-02-27 13:37:14,875:DEBUG:certbot.cli:Var server=https://acme-v02.api.letsencrypt.org/directory (set by user).
2019-02-27 13:37:14,875:DEBUG:certbot.cli:Var account=set(['server']) (set by user).
2019-02-27 13:37:15,780:DEBUG:certbot.storage:Writing new config /etc/letsencrypt/renewal/zwart-licht.nl.conf.
2019-02-27 13:37:15,781:DEBUG:certbot.reporter:Reporting to user: Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/zwart-licht.nl/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/zwart-licht.nl/privkey.pem
```
CLI information
```
# pwd
/etc/letsencrypt/live/zwart-licht.nl
# ll
total 4,0K
lrwxrwxrwx 1 root root 38 feb 27 13:37 cert.pem -> ../../archive/zwart-licht.nl/cert1.pem
lrwxrwxrwx 1 root root 39 feb 27 13:37 chain.pem -> ../../archive/zwart-licht.nl/chain1.pem
lrwxrwxrwx 1 root root 43 feb 27 13:37 fullchain.pem -> ../../archive/zwart-licht.nl/fullchain1.pem
lrwxrwxrwx 1 root root 41 feb 27 13:37 privkey.pem -> ../../archive/zwart-licht.nl/privkey1.pem
-rw-r--r-- 1 root root 692 feb 27 13:37 README
# pwd
/etc/letsencrypt/renewal
# cat zwart-licht.nl.conf
# renew_before_expiry = 30 days
version = 0.31.0
archive_dir = /etc/letsencrypt/archive/zwart-licht.nl
cert = /etc/letsencrypt/live/zwart-licht.nl/cert.pem
privkey = /etc/letsencrypt/live/zwart-licht.nl/privkey.pem
chain = /etc/letsencrypt/live/zwart-licht.nl/chain.pem
fullchain = /etc/letsencrypt/live/zwart-licht.nl/fullchain.pem
# Options used in the renewal process
[renewalparams]
account = ***
server = https://acme-v02.api.letsencrypt.org/directory
authenticator = webroot
rsa_key_size = 4096
webroot_path = /usr/local/ispconfig/interface/acme,
[[webroot_map]]
```3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5291Unable to initalize letsencrypt with subdomains2019-04-15T12:19:33ZRajko AlbrechtUnable to initalize letsencrypt with subdomains## short description
When setting up a site with auto subdomains enable of letsencrypt fails.
## environment
* Server OS: debian
* Server OS version: 9.8
* ISPConfig version: 3.1.13
* certbot: 0.33.1
* Apache/2.4.25 (Debian)
## Probl...## short description
When setting up a site with auto subdomains enable of letsencrypt fails.
## environment
* Server OS: debian
* Server OS version: 9.8
* ISPConfig version: 3.1.13
* certbot: 0.33.1
* Apache/2.4.25 (Debian)
## Problem behind
in `get_letsencrypt_certificate_paths` in `letsencrypt.inc.php` you try to read the related domains from renewal config files due reading the lines in section `[[webroot_map]]`
But sometimes (I don't know why) certbot does not write these lines into config file. So there is no certificate files given back to `request_certificates` and then letsencrypt is of course disabled.
A possible stable solution would, instead of parsing the config file of letsencrypt you may use the output of `certbot-auto certificates -d <maindomain> -d <subdomain> -d <subdomain>` which results always in a _single_ output of associated files like
```
Certificate Name: example.com
Domains: example.com www.example.com
Expiry Date: xxxxx (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/example.com/fullchain.pem
Private Key Path: /etc/letsencrypt/live/example.com/privkey.pem
```
I think parsing such a small blob would be more stable then reading of config files.3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5288Wrong permissions of dkim cert folder on CentOS 72019-04-08T16:34:07ZTill BrehmWrong permissions of dkim cert folder on CentOS 7The wrong permissions cause this error:
Error in config file "/etc/amavisd/amavisd.conf": Error in config file "/etc/amavisd/60-dkim": Can't open PEM file /var/lib/amavis/dkimThe wrong permissions cause this error:
Error in config file "/etc/amavisd/amavisd.conf": Error in config file "/etc/amavisd/60-dkim": Can't open PEM file /var/lib/amavis/dkim3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5218Add incron plugin2019-03-26T16:55:20ZWebsliceAdd incron pluginIt is feasible for us to allow our customers to reload PHP-FPM to clear the opcache, after they perform deployments of their PHP applications. To facilitate this we would like to add a plugin which creates a default incrond configuration.It is feasible for us to allow our customers to reload PHP-FPM to clear the opcache, after they perform deployments of their PHP applications. To facilitate this we would like to add a plugin which creates a default incrond configuration.3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5237DNS: xfer / also_notify fields too short2019-03-20T18:07:15ZKordian BruckDNS: xfer / also_notify fields too shortI need to add a longer list of IPs for transfer and notification to those fields. The DB columns are limited to `varchar(255)`. Can we change this to `TEXT`?
Example List:
```
109.201.133.61
108.59.2.202
79.137.84.65
46.165.221.164
185....I need to add a longer list of IPs for transfer and notification to those fields. The DB columns are limited to `varchar(255)`. Can we change this to `TEXT`?
Example List:
```
109.201.133.61
108.59.2.202
79.137.84.65
46.165.221.164
185.136.96.96
185.136.97.96
185.136.98.96
185.136.99.96
185.206.180.196
2a00:1768:1001:9::21
2604:9a00:2100:a006:4::1
2001:41d0:401:3100::5784
2a00:c98:2030:a006:2::1
2a06:fb00:1::1:96
2a06:fb00:1::2:96
2a06:fb00:1::3:96
2a06:fb00:1::4:96
2a0b:1640:1:3::4
```3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5275DNS Wizard does not add new zone2019-03-20T17:46:41ZTill BrehmDNS Wizard does not add new zoneThis issue existed in GIT stable branch temporarily only, the code was not part of any released version.This issue existed in GIT stable branch temporarily only, the code was not part of any released version.3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5216Send emails to active customers and resellers only.2019-03-11T11:38:14ZTill BrehmSend emails to active customers and resellers only.https://www.howtoforge.com/community/threads/send-email-function.81046/https://www.howtoforge.com/community/threads/send-email-function.81046/3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4977stats Folder created even when Statistics set to none2019-03-11T11:37:58ZAlfons L.stats Folder created even when Statistics set to noneOn every Website change in ISPConfig the **stats** Folder is getting created.
When using ownCloud or Nextcloud the Client is not able to do Updates because the Updater does a File Integrity Check first and aborts, because there should n...On every Website change in ISPConfig the **stats** Folder is getting created.
When using ownCloud or Nextcloud the Client is not able to do Updates because the Updater does a File Integrity Check first and aborts, because there should not additional Files/Folders like **stats**.
It would be the best to not create that Folder when "No Statistics" is choosen.
```
Technical information
=====================
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.
Results
=======
- core
- EXTRA_FILE
- stats/.htaccess
Raw output
==========
Array
(
[core] => Array
(
[EXTRA_FILE] => Array
(
[stats/.htaccess] => Array
(
[expected] =>
[current] => 5ef12b8cca40c9c40108f0b770ae77859b302b3011472090ed59be6ba6dbd335d4f53e66cd2089c308c800f4fb25a9b933e4bbc14c64864bd5aa988d5f0b9cba
)
)
)
)
```3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5253Server Config is having an error 500 with ISPConfig Version: 3.1.13p12019-03-05T17:13:45ZPagchen KelsangServer Config is having an error 500 with ISPConfig Version: 3.1.13p1Found a bug in file interface/web/admin/server_config_edit.php
line 110
`-- $app->tpl->setVar('server_name', $app->functions->htmlentities($app->db->queryOneRecord("SELECT server_name FROM server WHERE server_id = ? AND ((SELECT COUNT(*)...Found a bug in file interface/web/admin/server_config_edit.php
line 110
`-- $app->tpl->setVar('server_name', $app->functions->htmlentities($app->db->queryOneRecord("SELECT server_name FROM server WHERE server_id = ? AND ((SELECT COUNT(*) FROM server) > 1)", $this->id)['server_name']));`
`++ $app->tpl->setVar('server_name', $app->functions->htmlentities($app->db->queryOneRecord("SELECT server_name FROM server WHERE server_id = ? AND ((SELECT COUNT(*) FROM server) > 1)", $this->id)));`3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5219Run getmail only on master when server is a mirror2019-03-05T17:03:53ZTill BrehmRun getmail only on master when server is a mirrorhttps://www.howtoforge.com/community/threads/getmail-catch-emails-duplicate-on-servers-in-cluster.81076/https://www.howtoforge.com/community/threads/getmail-catch-emails-duplicate-on-servers-in-cluster.81076/3.1.14https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4972domain in spamfilter_user settings not punicode encoded2019-03-05T15:34:38ZTill Brehmdomain in spamfilter_user settings not punicode encodedWhen a mail domain with spamfilter enabled is saved to the spamfilter_users table, then the punicode filter is not applied correctly.When a mail domain with spamfilter enabled is saved to the spamfilter_users table, then the punicode filter is not applied correctly.3.1.14