ISPConfig 3 issueshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues2021-01-21T09:40:52Zhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5121Letsencrypt Info in Panel about Cert expire2021-01-21T09:40:52ZAlexLetsencrypt Info in Panel about Cert expireI think its good when Admin can see the the date of expire a cert and next Option become to create new cert for the web if I want.I think its good when Admin can see the the date of expire a cert and next Option become to create new cert for the web if I want.https://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/4781Improve SEO redirects2022-06-28T08:25:01ZTill BrehmImprove SEO redirectshttps://www.howtoforge.com/community/threads/seo-redirects-from-h-p-domain-tld-to-h-ps-x-domain-tld.77196/#post-364775https://www.howtoforge.com/community/threads/seo-redirects-from-h-p-domain-tld-to-h-ps-x-domain-tld.77196/#post-364775https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4697ISPconfig Debian packages2020-05-22T16:01:55ZHelmoISPconfig Debian packagesI noticed that ncomputers.org tried to make Debian packages of ISPconfig, as explained on:
https://www.howtoforge.com/tutorial/the-experimental-server-debian-stretch-apache-mysql-php-7-pure-ftpd-and-ispconfig-31/
Getting this stable wo...I noticed that ncomputers.org tried to make Debian packages of ISPconfig, as explained on:
https://www.howtoforge.com/tutorial/the-experimental-server-debian-stretch-apache-mysql-php-7-pure-ftpd-and-ispconfig-31/
Getting this stable would be appreciated :)
I'm opening this issue since I've been unable to find an issue about it or any other public discussion. Any comment's on this?https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4529Disable suggestions IP in DNS module2022-08-17T13:00:09ZAndyPLDisable suggestions IP in DNS moduleI set up a couple of local IP addresses and do not want to see their customers suggest this.
Whether and where it is possible opt these suggestions for people outside the group ADMIN?I set up a couple of local IP addresses and do not want to see their customers suggest this.
Whether and where it is possible opt these suggestions for people outside the group ADMIN?Jesse NorellJesse Norellhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4498Function for website snapshots2017-09-14T11:59:56ZTill BrehmFunction for website snapshotsAdd a function to make snapshots of websites by using hard links.Add a function to make snapshots of websites by using hard links.3.3Till BrehmTill Brehmhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4430Select sites by PHP version in ISPConfig2017-08-10T20:10:36ZTill BrehmSelect sites by PHP version in ISPConfigSelect sites by PHP version in ISPConfigSelect sites by PHP version in ISPConfighttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4386rfe: better DNS suggestions2022-08-17T13:00:12ZJesse Norellrfe: better DNS suggestionsWhen a client adds DNS records, the IP-Address suggestions provides a long list of IP addresses that is largely useless; in the common case we see they are simply IP addresses that other clients have entered, including those which are pr...When a client adds DNS records, the IP-Address suggestions provides a long list of IP addresses that is largely useless; in the common case we see they are simply IP addresses that other clients have entered, including those which are private/internal to the other client's network, or explicitly assigned to a (different) client undre System > Server IP Addresses, and hence unavailable to use. I'd like the ability to control/limit what addresses show up in the list of suggestions, or to provide better suggestions.
Without explicit control of the list, rather than suggesting "all system ip addrs + every address any client has ever entered", it would be better with something like "all web, mail and db servers currently used by the client + all system ip addrs available to the client (not assigned to other clients) + all ip addresses this client (only) as previously entered".Jesse NorellJesse Norellhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4315Let's Encrypt ECC certificates2020-09-25T21:22:49ZTomas Frantikhi@tomasfrantik.euLet's Encrypt ECC certificatesHello,
I wonder if you plan to add more options for generating Let's Encrypt certificates. Primarily (for me) a possibility to choose between cert types like RSA or ECC 256bit or ECC 384bit - both ECC with fields for creating csr or wit...Hello,
I wonder if you plan to add more options for generating Let's Encrypt certificates. Primarily (for me) a possibility to choose between cert types like RSA or ECC 256bit or ECC 384bit - both ECC with fields for creating csr or with csr from Web Domain > SSL admin section. Thanks :)https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4174[3.1rc1] Show "Move Spam Emails to Junk directory.:" to mail user2019-10-24T05:27:50ZJohan Ehnberg[3.1rc1] Show "Move Spam Emails to Junk directory.:" to mail userSimple feature request: when the Mail Filter/Email Filters tab is shown to mail users as per interface settings, currently only the list of filters is shown. In the admin view, there is a very handy "Move Spam Emails to Junk directory.:"...Simple feature request: when the Mail Filter/Email Filters tab is shown to mail users as per interface settings, currently only the list of filters is shown. In the admin view, there is a very handy "Move Spam Emails to Junk directory.:" checkbox that mail users could benefit from.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4110Let's Encrypt certbot-auto output not logged in a usable manner, only "Let's ...2020-08-08T13:27:18ZJohan EhnbergLet's Encrypt certbot-auto output not logged in a usable manner, only "Let's Encrypt SSL Cert for: example.com could not be issued."When Let's Encrypt certbot-auto fails, the only error in the System-Log is:
Let's Encrypt SSL Cert for: example.com could not be issued.
There are no other logs that I can find around the server that would explain more, and the error...When Let's Encrypt certbot-auto fails, the only error in the System-Log is:
Let's Encrypt SSL Cert for: example.com could not be issued.
There are no other logs that I can find around the server that would explain more, and the error above is not helpful when it fails.
When running certbot-auto from the command line, there is plenty of helpful output for both successes and failures.
This is on 3.1dev.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4074reseller support in Help module2017-08-10T20:10:43ZJesse Norellreseller support in Help modulefeature request: I'd like to setup the Help module to answer faq's and send/receive messages, but it's not reseller aware. Any support messages sent by a client should go to the reseller, not the server admin. And many of the faq's wo...feature request: I'd like to setup the Help module to answer faq's and send/receive messages, but it's not reseller aware. Any support messages sent by a client should go to the reseller, not the server admin. And many of the faq's would have reseller-specific info in them (eg. contact info, what nameservers should be registered, etc...).https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4021Webalizer GeoIP disabled2017-08-10T20:10:44ZSteffen NielsenWebalizer GeoIP disabledThe parameters GeoIP and GeoIPDatabase seems to be disabled for all sites that enables webalizer which results in a useless pie chart showing 100% unknown locations. Simply enabling those two parameters within /var/www/domain/log/webaliz...The parameters GeoIP and GeoIPDatabase seems to be disabled for all sites that enables webalizer which results in a useless pie chart showing 100% unknown locations. Simply enabling those two parameters within /var/www/domain/log/webalizer.conf enables geolocation statistics for that website.
[geo-chart](/uploads/bc4bbf7961b477fa01782af2ee750169/geo-chart.png).https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3818Implement trusted hostname for web panel ( ? )2020-09-15T15:40:09ZNick AndriopoulosImplement trusted hostname for web panel ( ? )Currently (`3.0.5.4p9`), at least when Apache is used, the ISPConfig panel is accessible on the port defined during installation, regardless of the hostname even if one is provided during install.
As an example, if I ask the install...Currently (`3.0.5.4p9`), at least when Apache is used, the ISPConfig panel is accessible on the port defined during installation, regardless of the hostname even if one is provided during install.
As an example, if I ask the installer to have SSL enabled for the `example.com` domain on port `8080`, my panel is accessible at `https://example.com:8080` .
When clients are hosted on the same IP, `https://clientdomain.com:8080` will also take them to the panel page. I am uncertain whether this is a desired behavior, but my personal preference would be to have the option to limit ISPConfig panel access to the FQDN defined in the installer script.
It is trivial to fix (I currently patch it), by changing the generated ispconfig.vhost so that the
<VirtualHost _default_:8080>
line is replaced by a simple virtualhost that produces a 404, and the actual configuration resides in a virtualhost with the proper FQDN:
<VirtualHost _default_:8080>
DocumentRoot "/var/sample/404"
</VirtualHost>
<VirtualHost *:8080>
ServerName myfqdn.com
`_default_:8080` Virtualhost produces a 404, and include all the configuration on a <FQDN>:8080 virtualhost
I am uncertain whether this would be of general use, however it is standard practice for my servers, and was wondering if it is something that others might find useful as well.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3707Force password on first login" setting2020-08-08T13:08:38ZTill BrehmForce password on first login" settingThat way when we provide access to a user it is a secure way to email a password that we know can only be utilized by one user - and confirm that only that user utilized it.That way when we provide access to a user it is a secure way to email a password that we know can only be utilized by one user - and confirm that only that user utilized it.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3652Integrate imapsync instead of getmail (imap)2019-11-04T11:38:25ZSteffen NielsenIntegrate imapsync instead of getmail (imap)imapsync seems easy to install and use and even supports sync of subfolders which getmail doesn't.
https://github.com/imapsync/imapsync
Found installation notes on: http://blog.grossi.io/2013/migrating-emails-using-imap-imapsync-to...imapsync seems easy to install and use and even supports sync of subfolders which getmail doesn't.
https://github.com/imapsync/imapsync
Found installation notes on: http://blog.grossi.io/2013/migrating-emails-using-imap-imapsync-tofrom-gmail-yahoo-etc/https://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/2889make ispconfig compatible with mysql strict mode2020-09-18T16:41:42ZTill Brehmmake ispconfig compatible with mysql strict modehttp://www.howtoforge.com/forums/showthread.php?t=63612http://www.howtoforge.com/forums/showthread.php?t=63612Planned features