ISPConfig 3 issueshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues2018-12-15T18:14:17Zhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4231WARNING - Falsche Anfrage / Wrong QuerySQL-Query = UPDATE web_domain2018-12-15T18:14:17ZAntalWARNING - Falsche Anfrage / Wrong QuerySQL-Query = UPDATE web_domainI just enabled SSL + letsencrypt on a website on my slave server and got the error below. I've updated both servers and chose to reconfigure permissions.
WARNING - Falsche Anfrage / Wrong QuerySQL-Query = UPDATE web_domain SET `ssl` =...I just enabled SSL + letsencrypt on a website on my slave server and got the error below. I've updated both servers and chose to reconfigure permissions.
WARNING - Falsche Anfrage / Wrong QuerySQL-Query = UPDATE web_domain SET `ssl` = 'n', `ssl_letsencrypt` = 'n' WHERE `domain` = 'domain.tld' -> 1143 (UPDATE command denied to user 'ispcsrv4'@'server2.domainserver.tld' for column 'ssl' in table 'web_domain')3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4240Falsche Anfrage / Wrong QuerySQL when letsencrypt fails2018-12-15T18:14:17ZPascal DreissenFalsche Anfrage / Wrong QuerySQL when letsencrypt failsWhen requesting an letsencrypt certificate, and for whatever reason the request fails i'm receiving the following error message:
02.10.2016-13:16 - WARNING - Falsche Anfrage / Wrong QuerySQL-Query = UPDATE web_domain SET `ssl` = 'y', ...When requesting an letsencrypt certificate, and for whatever reason the request fails i'm receiving the following error message:
02.10.2016-13:16 - WARNING - Falsche Anfrage / Wrong QuerySQL-Query = UPDATE web_domain SET `ssl` = 'y', `ssl_letsencrypt` = 'n' WHERE `domain` = 'cxxx.xx' -> 1143 (UPDATE command denied to user 'ispcsrv12'@'xxxx' for column 'ssl' in table 'web_domain')
When updating and running: Reconfigure Permissions in master database ? does not fix the problem.
Digging into the update or installer code (installer_base.lib.php) specific the function: grant_master_database_rights i found out that for the web_domain table only the following columns are granted for the ispcsrv account: `ssl_request`, `ssl_cert`, `ssl_action`, `ssl_key`. I think we are missing the following 2 column also (which would fix the above error message): `ssl`, `ssl_letsencrypt`
Will create a merge request for this.3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4242Add secondary DNS api functions2018-12-15T18:14:17ZTill BrehmAdd secondary DNS api functionshttps://www.howtoforge.com/community/threads/create-delete-secondary-dns-with-remote-api.74136/https://www.howtoforge.com/community/threads/create-delete-secondary-dns-with-remote-api.74136/3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4252Check if virtual cron system obeys error reporting levels2018-12-15T18:14:17ZTill BrehmCheck if virtual cron system obeys error reporting levelshttps://www.howtoforge.com/community/threads/ispc-cronlog-logs-everything.74160/#post-349061https://www.howtoforge.com/community/threads/ispc-cronlog-logs-everything.74160/#post-3490613.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4271Creating vHost Website Alias copies default index.html thus breaking the orig...2018-12-15T18:14:15ZJanThielCreating vHost Website Alias copies default index.html thus breaking the original site if it's based on index.php (or something not index.html)Already described here but still existing:
https://www.howtoforge.com/community/threads/vhost-alias-domains-with-own-ssl-certificates.73842/#post-347451
ISPC Version: Latest 3.1 Major Release Version
**Steps to reproduce:**
1. Create...Already described here but still existing:
https://www.howtoforge.com/community/threads/vhost-alias-domains-with-own-ssl-certificates.73842/#post-347451
ISPC Version: Latest 3.1 Major Release Version
**Steps to reproduce:**
1. Create a Website in ISPC
2. Delete all the Default files in the websites "web" folder and put an "index.php" in place (as if you would install any major Web CMS or whatever PHP application)
3. Enable the "Aliasdomain (Vhost)" Feature
4. Create an Aliasdomain (Vhost) targeting the Website created in 1
**Issue:**
After this procedure, the Website will be broken, as the Aliasdomain (Vhost) will again copy the default files to its "web" directory which is symlinked to the main Websites folder. As the index.html is first in order for index files, the index.php is ignored and my website is broken. I did not test, if an existing index.html would be overwritten. But this might be possible as well.
**Expected behaviour:**
No default files are copied, if I create an Aliasdomain (Vhost).3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4302Main domain not included in generated Lest's encrypt certificate2018-12-15T18:14:15ZMiroslav StaroňMain domain not included in generated Lest's encrypt certificateHi,
in genereted SSL certificates in my instalation is not included main domain for site. There is www.doman.tld (if main domain is non-www) and alias domains but not main domain (domain.tld).
Maybe the problem is in $temp_domains[] va...Hi,
in genereted SSL certificates in my instalation is not included main domain for site. There is www.doman.tld (if main domain is non-www) and alias domains but not main domain (domain.tld).
Maybe the problem is in $temp_domains[] variable in apache2_plugin.inc3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4135Mailman /var/lib/mailman/data/*-mailman empty after upgrade to 3.1-RC12018-04-30T07:46:28ZSebastianMailman /var/lib/mailman/data/*-mailman empty after upgrade to 3.1-RC1Hi,
just noticed after upgrading to 3.1-RC1 that my /var/lib/mailman/data/virtual-mailman and /var/lib/mailman/data/transport-mailman files are empty.
I noticed it by watching a mail.log error complaining that virtual-mailman.db is old...Hi,
just noticed after upgrading to 3.1-RC1 that my /var/lib/mailman/data/virtual-mailman and /var/lib/mailman/data/transport-mailman files are empty.
I noticed it by watching a mail.log error complaining that virtual-mailman.db is older than virtual-mailman.
I added a new list in ispconfig admin panel, the new list is now referenced in the files and working, both old lists are not.
Edit: Also, if I delete the newly created list, their reference is not purged from virtual-mailman or transport-mailman.
3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/3878function filter_var missing2017-08-10T20:10:35ZJohan Guerrerosfunction filter_var missingi want to change a mailbox password and when i click on the save button this error appear also i cant change to any other tab.i want to change a mailbox password and when i click on the save button this error appear also i cant change to any other tab.3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4029client_delete_everything API only database entries removed2017-08-10T20:10:33ZDanielclient_delete_everything API only database entries removedWhen trying to delete a client using the API, function client_delete_everything, it seems that only the database entries are deleted. Databases, FTP, web path directories/files are all left on the server and have to be deleted manually (...When trying to delete a client using the API, function client_delete_everything, it seems that only the database entries are deleted. Databases, FTP, web path directories/files are all left on the server and have to be deleted manually (not from ispconfig panel, as they are not listed there any more).
As I know, the same function deleted everything from the system. Deleting the client from the panel works.
Will look into this soon, but someone may have an idea what is happening?3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4264wrong client name in databases quota2017-07-16T07:50:01ZLuboswrong client name in databases quotaIn menu Sites: Statistics: Database quota.
Wrong client name. Each database has a client name admin.
In menu Sites: Databases: Database user.
it would be good to add the client's nameIn menu Sites: Statistics: Database quota.
Wrong client name. Each database has a client name admin.
In menu Sites: Databases: Database user.
it would be good to add the client's name3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4307Letsencrypt + nginx broken with ISPConf 3.1.1 due to "-le" suffix in .crt & ....2017-06-25T10:54:20ZJanThielLetsencrypt + nginx broken with ISPConf 3.1.1 due to "-le" suffix in .crt & .key symlinksHi,
after upgrading from stable 3.1 to stable 3.1.1 the LE SSL files are linked with a "-le" suffix to ${WEB_ROOT}/ssl. The apache Template reflects this correctly thanks to https://git.ispconfig.org/ispconfig/ispconfig3/commit/f90e18f...Hi,
after upgrading from stable 3.1 to stable 3.1.1 the LE SSL files are linked with a "-le" suffix to ${WEB_ROOT}/ssl. The apache Template reflects this correctly thanks to https://git.ispconfig.org/ispconfig/ispconfig3/commit/f90e18f6826392c02031fe458df70d22528926c4
Sadly the nginx vhost template does not yet reflect this change and tries to include $ssl_domain.crt and $ssl_domain.key which do not exist anymore.
In `nginx_plugin.inc.php`
`$csr_file = $ssl_dir.'/'.$domain.'.csr';
$crt_file = $ssl_dir.'/'.$domain.'.crt';
`
And in `nginx_vhost.master`
`ssl_certificate <tmpl_var name='document_root'>/ssl/<tmpl_var name='ssl_domain'>.crt;
ssl_certificate_key <tmpl_var name='document_root'>/ssl/<tmpl_var name='ssl_domain'>.key;
`
As a hotfix, we are manually reverting the "-le" suffixing in `nginx_plugin.inc.php` lines 1239 and following by commenting them out. But this is just a hotfix. If I looked correctly there are some bigger code changes in the master already. But as this totaly breaks nginx + LE I feel this has to be addressed more urgently.
Already tried to update to git-stable without any luck.
Best Regards,
Jan3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4299SSL certificate key mismatch problem2017-06-25T10:54:20ZTill BrehmSSL certificate key mismatch problemThe problem occurs when a custom ssl ert has been used before in a website, when you activate letsencrypt then and letsencrypt fails to validate a cert, then the key from letsencrypt is used with the old custom ssl cert which causes apac...The problem occurs when a custom ssl ert has been used before in a website, when you activate letsencrypt then and letsencrypt fails to validate a cert, then the key from letsencrypt is used with the old custom ssl cert which causes apache to fail to start.3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4291System Config2017-06-25T10:54:20ZbrodySystem Configwhen adding ( [quota] [databasequota] [mailquota] [limits] ) in Main Config -> misc , Left Admin Dashlets. Account limits shows twicewhen adding ( [quota] [databasequota] [mailquota] [limits] ) in Main Config -> misc , Left Admin Dashlets. Account limits shows twice3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4289ISPConfig shows a warning when an additional template is added to a client2017-06-25T10:54:20ZTill BrehmISPConfig shows a warning when an additional template is added to a clientISPConfig shows a warning when an additional template is added to a client. No warning is shown at the reseller.ISPConfig shows a warning when an additional template is added to a client. No warning is shown at the reseller.3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4267ISPConfig 3.1 - wrong page jump in FTP traffic module2017-06-25T10:54:20ZOndrejISPConfig 3.1 - wrong page jump in FTP traffic moduleHi guys,
when i go to Sites -> FTP traffic, paging is not working
- there's 15 entries displayed by default
- when i want to go e.g. to page 2, Web traffic page 2 is displayed instead
Let me know in case you will need to deliver any oth...Hi guys,
when i go to Sites -> FTP traffic, paging is not working
- there's 15 entries displayed by default
- when i want to go e.g. to page 2, Web traffic page 2 is displayed instead
Let me know in case you will need to deliver any other info about those issues.
Thanks :)3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4257XFS quota not working correctly2017-06-25T10:54:20ZMarius BurkardXFS quota not working correctlyISPConfig cron job gives `xfs_quota: ungültiger Gruppenname: webX`ISPConfig cron job gives `xfs_quota: ungültiger Gruppenname: webX`3.1.1Marius BurkardMarius Burkardhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/42553.1 Remote API - sites_database_user_delete should DROP user from mysql user ...2017-06-25T10:54:20ZChristian3.1 Remote API - sites_database_user_delete should DROP user from mysql user tablesites_database_user_delete should DROP user from mysql user table, not only from ispconfig DB.
Reason:
I run "sites_database_delete" to delete and DROP a database.
When a database user is in ispconfig DB it will be DROPPED fr...sites_database_user_delete should DROP user from mysql user table, not only from ispconfig DB.
Reason:
I run "sites_database_delete" to delete and DROP a database.
When a database user is in ispconfig DB it will be DROPPED from mysql user table, but not deleted from ispconfig DB.
to delete the database user from ispconfig i run "sites_database_user_delete", but this deletes the user before "db_delete" is ran by ispconfig cron.
my workaround is to set a timeout before running "sites_database_user_delete" and hope the DB and user is correctly dropped, because i have no chance to check if the database is already deleted, because "sites_database_delete" already deleted it from ispconfig DB.3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4249System php.ini is not included in custom php.ini2017-06-25T10:54:20ZTill BrehmSystem php.ini is not included in custom php.iniISPConfig normally adds the system php.ini file content in the custom php.ini file. This seems to be broken in 3.1 at the moment.ISPConfig normally adds the system php.ini file content in the custom php.ini file. This seems to be broken in 3.1 at the moment.3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4241Missing newlines in Apache 2.2 vhost templates2017-06-25T10:54:20ZTill BrehmMissing newlines in Apache 2.2 vhost templatesThere are 3 places in the vhost templates for apache 2.2 (not 2.4) where a newline is missing when letsencrypt is enabled. This will cause the creation of the letsencrypt cert to fail.There are 3 places in the vhost templates for apache 2.2 (not 2.4) where a newline is missing when letsencrypt is enabled. This will cause the creation of the letsencrypt cert to fail.3.1.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4237Add a workaround for broken IDN extensions in some PHP versions2017-06-25T10:54:20ZTill BrehmAdd a workaround for broken IDN extensions in some PHP versionshttps://www.howtoforge.com/community/threads/problems-after-upgrading-to-3-1.74075/#post-348462https://www.howtoforge.com/community/threads/problems-after-upgrading-to-3-1.74075/#post-3484623.1.1Marius BurkardMarius Burkard