ISPConfig 3 issueshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues2022-03-04T23:44:23Zhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6143postfix: custom reject message2022-03-04T23:44:23ZJesse Norellpostfix: custom reject messageAdd a field for custom reject message to postfix blacklist entries.Add a field for custom reject message to postfix blacklist entries.Planned featuresJesse NorellJesse Norellhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5844Incorrect language management2020-10-23T12:25:08Zcubellsvicent@vcubells.netIncorrect language managementI speak catalan language, and iso 639-1 code for catalan language is **ca**
As you can see in this capture:
![ispconfig_languages_issue](/uploads/37dad9acc67e9bf0477c0203385e026d/ispconfig_languages_issue.png)
I can't create language...I speak catalan language, and iso 639-1 code for catalan language is **ca**
As you can see in this capture:
![ispconfig_languages_issue](/uploads/37dad9acc67e9bf0477c0203385e026d/ispconfig_languages_issue.png)
I can't create language templates for catalan language because **ca** code is taken by Canada country.
Ispconfig is managing languages incorrectly, among other things, because we are confusing country codes and language codes.
Ispconfig must handle better language codes as another free software applications do.
Reference: https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes#CAPlanned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5172Feature Request: Create only new certificate request2018-11-01T18:41:00ZRaffael LuthigerFeature Request: Create only new certificate requestI have a domain where we already have a certificate (and private key). Now I would like to create a new request without changing the key and without changing the certificate and bundle.
For this I would like to have a new "SSL action" w...I have a domain where we already have a certificate (and private key). Now I would like to create a new request without changing the key and without changing the certificate and bundle.
For this I would like to have a new "SSL action" with the name "Create certificate request" which will then only generate a new request.Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5086Show name of deleted item in delete confirmation dialog2018-07-20T17:41:57ZTill BrehmShow name of deleted item in delete confirmation dialogShow name of deleted item in delete confirmation dialogShow name of deleted item in delete confirmation dialogPlanned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5041Suspending a client2020-08-28T17:55:09ZSteffen NielsenSuspending a clientI'm trying to suspend a client from API by changing
```
$params['canceled'] = 'y';
$params['locked'] = 'y';
```
These are submitted to the client_update() function which is reflected in the interface marking respectively the checkboxes...I'm trying to suspend a client from API by changing
```
$params['canceled'] = 'y';
$params['locked'] = 'y';
```
These are submitted to the client_update() function which is reflected in the interface marking respectively the checkboxes "Locked" and "Canceled" as activated. However this doesn't seem to have any impact on the client being able to login or not or neither does it seem to have impact on the client's websites, maildomains etc. being deactivated.
Marking Locked and Canceled in the interface manually works fine.
Am i missing something?Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4846Integrate Cloudflare & StopTheHacker website Addition2021-05-20T14:24:44ZRich StarkieIntegrate Cloudflare & StopTheHacker website AdditionIs it possible to add in the ability to add a website (and automatically configure dns) to cloudflare and/or stopthehacker naturally only free plan sites could be added.
An API is available, I assume, as the facility is available in t...Is it possible to add in the ability to add a website (and automatically configure dns) to cloudflare and/or stopthehacker naturally only free plan sites could be added.
An API is available, I assume, as the facility is available in the likes of cPanel and PleskPlanned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4794Add support for nginx.org debian packages2020-09-25T21:42:10ZTill BrehmAdd support for nginx.org debian packagesAdd support for the debian packages from nginx.org instead of the nginx packages from the Debian main repository. See #4743 for details.Add support for the debian packages from nginx.org instead of the nginx packages from the Debian main repository. See #4743 for details.Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4698Show mail server details in mailbox details2020-03-29T18:17:11ZTill BrehmShow mail server details in mailbox detailsAdd an option to show the mail server details like pop3/imap server, port, etc. in mailbox details. The most flexible solution ill probably a free text field in server settings where the admin can add a text that is shown to clients in t...Add an option to show the mail server details like pop3/imap server, port, etc. in mailbox details. The most flexible solution ill probably a free text field in server settings where the admin can add a text that is shown to clients in the mailbox settings.Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4624Extend nginx directives merge features2020-09-25T21:37:13ZTill BrehmExtend nginx directives merge featuresImplement another command like ##before## to put something in front of a section or something like ##mergestart## to put the merged code at the beginning of the section and not at the end.Implement another command like ##before## to put something in front of a section or something like ##mergestart## to put the merged code at the beginning of the section and not at the end.Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4451[ISPC 3.1.2] Document Root Nginx patch2017-12-27T04:31:24ZAndyPL[ISPC 3.1.2] Document Root Nginx patchTo work properly the patch must be added to the database field web_root
```
ALTER TABLE `web_domain`
ADD COLUMN `web_root` VARCHAR(255) NULL DEFAULT NULL AFTER `folder_directive_snippets`;
```
[nginx-docroot.diff](/uploads/50d6...To work properly the patch must be added to the database field web_root
```
ALTER TABLE `web_domain`
ADD COLUMN `web_root` VARCHAR(255) NULL DEFAULT NULL AFTER `folder_directive_snippets`;
```
[nginx-docroot.diff](/uploads/50d616ff9b32a1fb79d5306c3ee95fa4/nginx-docroot.diff)Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3940Add SFTP (via SSH) as (better) alternative to FTP(S) Users2021-09-28T16:32:10ZJens GrohAdd SFTP (via SSH) as (better) alternative to FTP(S) UsersAdd the Option to create an SFTP User instead of having to run pure-ftpd and use this age-old protocol. FTP/S is an OK'ish workaround for secure transmission of data, but having the option to use SFTP for file transfer uploads would be m...Add the Option to create an SFTP User instead of having to run pure-ftpd and use this age-old protocol. FTP/S is an OK'ish workaround for secure transmission of data, but having the option to use SFTP for file transfer uploads would be much better.
SFTP could be used via an addition to the OpenSSH server configuration by adding an option set for a specific group or groups (e.g. sftponly) to force those upload account to only be used for SFTP and not provide a login shell.
As the "webXY" users already exist and point to a directory (/var/www/clients/clientXX/webXY) that is owned by root:root, the requirements for SFTP chrooting are already given. Those SFTP accounts could be created just like the Shell Users function with the exceptions given above.
The following snippet would provide a safe chroot environment
# SFTP Only Users
Match Group sftponly
X11Forwarding no
AllowTcpForwarding no
ChrootDirectory %h
ForceCommand internal-sftp
A user (e.g. sftp19_webspace) would just get its homedir (e.g. /var/www/clients/client5/web19) without providing a shell (in /etc/passwd) and would get sftp-only as group so to force the chroot active.
Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3726client filter in top menu2017-08-10T20:10:47ZAntalclient filter in top menuPlease consider a client filter in the top menu, only display items for the selected client and be able to deleted everything just like I can do as an admin.
Log in as client, does not provide all abilities an admin has and is too muc...Please consider a client filter in the top menu, only display items for the selected client and be able to deleted everything just like I can do as an admin.
Log in as client, does not provide all abilities an admin has and is too much of a hassle.
The system wide filter would save a lot of time and system resources when switching tabs.Planned featuresMarius BurkardMarius Burkardhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3708Support NodeJS2020-04-05T07:54:52ZLeonhard WolfmayrSupport NodeJSAs discussed in this thread: https://www.howtoforge.com/community/threads/support-for-nodejs.71538/#post-336594
NodeJS will be used much more widely if Wordpress makes the switch. ISPConfig should definitely support it then.As discussed in this thread: https://www.howtoforge.com/community/threads/support-for-nodejs.71538/#post-336594
NodeJS will be used much more widely if Wordpress makes the switch. ISPConfig should definitely support it then.Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3654Syntax error in "Custom php.ini settings" field causes php-fpm to go down; ch...2020-01-08T11:58:49ZBen JohnsonSyntax error in "Custom php.ini settings" field causes php-fpm to go down; check with FPM's --testHello!
While editing a virtual host's "Custom php.ini settings" value, I entered the following, which contains a superfluous and erroneous "&":
[code]
error_reporting = E_ALL & & ~E_DEPRECATED
[/code]
This is, of course, synta...Hello!
While editing a virtual host's "Custom php.ini settings" value, I entered the following, which contains a superfluous and erroneous "&":
[code]
error_reporting = E_ALL & & ~E_DEPRECATED
[/code]
This is, of course, syntactically invalid. But ISPConfig went ahead and attempted to restart php-fpm anyway, which resulted in a PHP outage across every site on the server, because php-fpm was stopped but never restarted (due to the syntax error that ISPConfig saved to the configuration).
Given that php-fpm has a built-in mechanism for validating its configuration, ISPConfig should make use of this feature.
If ISPConfig is already using "php-fpm --test", then something is not working correctly, because I just tested this very example and it is caught as expected:
# php-fpm --test PHP: syntax error, unexpected '&' in Unknown on line 1
[09-Sep-2015 09:56:23] ERROR: Unable to include /usr/local/zend/etc/fpm.d/web4.conf from /usr/local/zend/etc/php-fpm.conf at line 24
[09-Sep-2015 09:56:23] ERROR: failed to load configuration file '/usr/local/zend/etc/php-fpm.conf'
[09-Sep-2015 09:56:23] ERROR: FPM initialization failed
Calling "php-fpm --test" returns "0" status code if the configuration is valid, and a non-zero code if it is invalid. This should make it relatively simple to test the configuration before reloading PHP-FPM, rolling-back if necessary.
This is exactly what is done with NGINX and Apache configuration changes, so the same should be applied to other services, such as PHP, wherever possible.Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3532Add dynamic reject with postfix verify service2020-09-25T20:35:26ZTill BrehmAdd dynamic reject with postfix verify serviceAdd a dynmic reject configuration by using the postfix verify service for systems that use transports in fron of other mail servers like exchange servers.Add a dynmic reject configuration by using the postfix verify service for systems that use transports in fron of other mail servers like exchange servers.Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3494Allow enable/disable directive snippets for clients2020-11-01T16:11:59ZsdafsadfsdAllow enable/disable directive snippets for clientsI know that apache and php additional options are disabled for clients/resellers due to security as they can potentially break the whole webserver setup. However it is still needed to allow clients/resellers to enable some options in cer...I know that apache and php additional options are disabled for clients/resellers due to security as they can potentially break the whole webserver setup. However it is still needed to allow clients/resellers to enable some options in certain situations. My suggestions is to allow them to simply include some of the predefined snippets. I.e. the snippets that are added in the Directive snippets section are available as a list of checkboxes which resellers/clients can simply enable or disable.Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3253Add ip address filter to suggest IP function2017-08-10T20:10:58ZTill BrehmAdd ip address filter to suggest IP functionRefer to: #3206Refer to: #3206Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3224uid/gid inconsistency on multi-server setup2017-08-10T20:10:58Zdoekiauid/gid inconsistency on multi-server setupWhile using multi-server setup, uid/gid are fenced per server.
This causes inconsistency when migration sites inbetween servers and/or when settings server mirror of another one.
The same issue occurs when one server been installed w...While using multi-server setup, uid/gid are fenced per server.
This causes inconsistency when migration sites inbetween servers and/or when settings server mirror of another one.
The same issue occurs when one server been installed without some feature (such as mail) and configuring later the server to became mirror of one having the email feature ... uid starts on one at 5000 while they starts at 1000 on the other.
IMHO uid/give should be kept unique accross all servers - web1 on server1 should not share uid of web2 on server2
Best,Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3100Recipient for cron-errors2023-12-03T21:18:07ZDavid StillerRecipient for cron-errorsIt would be nice if the "MAILTO:"-directive would be maintained by ISPConfig too, for each job.It would be nice if the "MAILTO:"-directive would be maintained by ISPConfig too, for each job.Planned featureshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3036Add a check if there is enough space in /etc, before writing config file changes2020-08-28T19:04:57ZTill BrehmAdd a check if there is enough space in /etc, before writing config file changesAdd a check if there is enough space in /etc, before writing config file changesAdd a check if there is enough space in /etc, before writing config file changesPlanned features