ISPConfig 3 issueshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues2018-01-11T15:54:06Zhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4910Do not permit to add subdomains of domain acme.invalid2018-01-11T15:54:06ZTill BrehmDo not permit to add subdomains of domain acme.invalidDo not permit to add subdomains of domain acme.invalid in ISPConfig as a precaution for Let's Encrypt - TLS-SNI-01 issue. ISPConfig itself uses webroot auth with Certbot, so SSL certs that were generated with the LE option in ISPConfig a...Do not permit to add subdomains of domain acme.invalid in ISPConfig as a precaution for Let's Encrypt - TLS-SNI-01 issue. ISPConfig itself uses webroot auth with Certbot, so SSL certs that were generated with the LE option in ISPConfig are not affected by this issue.3.1.11https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4909Custom ISPConfig admin password not set, except Debian and Ubuntu2018-01-11T13:39:25ZTill BrehmCustom ISPConfig admin password not set, except Debian and UbuntuCustom ISPConfig admin password not set on centOS, OpenSuSE and Gentoo.Custom ISPConfig admin password not set on centOS, OpenSuSE and Gentoo.3.1.11https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4904issue on email foward form after commit which add filter on form2018-01-11T13:23:30ZGhost Userissue on email foward form after commit which add filter on form## short description
What is happening and what is wrong with that?
When I create/modify an "email forward" if I write in the destination field one email per line (\n\r) after saving I see in destination field all email addresses concat...## short description
What is happening and what is wrong with that?
When I create/modify an "email forward" if I write in the destination field one email per line (\n\r) after saving I see in destination field all email addresses concatenated on the same line without space.
Example:
---
foo@bar.org
john@doe.inc
---
become
---
foo@bar.orgjohn@doe.inc
---
## correct behaviour
What should happen instead?
it should stay:
foo@bar.org
john@doe.inc
## environment
Server OS: ubuntu
Server OS version: xenial
ISPConfig version: 3.1.10
## source
commit: ecbdda9b88a611f1653079ae64e4d7012157ce55 by adding filter in the form3.1.11Till BrehmTill Brehmhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4903Extend IDS system to allow different settings for clients and admin2018-01-11T13:23:13ZTill BrehmExtend IDS system to allow different settings for clients and adminExtend the internal ISPConfig Intrusion Detection System (IDS) to allow different settngs for the Admin, Client and not logged in users.Extend the internal ISPConfig Intrusion Detection System (IDS) to allow different settngs for the Admin, Client and not logged in users.3.1.11Till BrehmTill Brehmhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4902Stored XSS issue in autoresponder subject field2018-01-26T09:02:00ZTill BrehmStored XSS issue in autoresponder subject fieldA stored XSS vulnerability has been found in the subject field of the email autoresponder. Exploiting this issue requires a valid ISPConfig login.
Thank you to Fábián Patrik for reporting this issue.A stored XSS vulnerability has been found in the subject field of the email autoresponder. Exploiting this issue requires a valid ISPConfig login.
Thank you to Fábián Patrik for reporting this issue.3.1.11Marius BurkardMarius Burkardhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4898Reflected XSS issue in DNS module2018-01-11T13:22:36ZTill BrehmReflected XSS issue in DNS moduleA reflected XSS issue has been found in the DNS module. The XSS string is not stored in ISPConfig.
Thank you to Fábián Patrik for reporting this problem.A reflected XSS issue has been found in the DNS module. The XSS string is not stored in ISPConfig.
Thank you to Fábián Patrik for reporting this problem.3.1.11Till BrehmTill Brehmhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4879spamfilter_wblist - Entrys remain in DB after Customer Delete2018-01-11T13:22:06ZWHOspamfilter_wblist - Entrys remain in DB after Customer Delete## short description
Entrys of spamfilter_wblist remain after client deletion.
This happens if rid is 0 and also when the foreign key spamfilter_wblist.rid is = spamfilter_users.id
is set.
## correct behaviour
Deletion when User ist de...## short description
Entrys of spamfilter_wblist remain after client deletion.
This happens if rid is 0 and also when the foreign key spamfilter_wblist.rid is = spamfilter_users.id
is set.
## correct behaviour
Deletion when User ist deleted
## environment
Server OS: Debian
Server OS version: Stretch
ISPConfig version: 3.1.7 p1
_you can use `grep 'ISPC_APP_VERSION' /usr/local/ispconfig/server/lib/config.inc.php` to get it from the command line_
```
insert the output of `nginx -v` or `apachectl -v` here
Server version: Apache/2.4.25 (Debian)
Server built: 2017-09-19T18:58:57
insert the output of `php -v` here
PHP 7.0.19-1 (cli) (built: May 11 2017 14:04:47) ( NTS )
## proposed fix
optional, of course.
if you want to post code snippets, please use
```
## 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)
```3.1.11Till BrehmTill Brehmhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4865Client folder remains after deletion2018-01-11T13:21:55ZWHOClient folder remains after deletion## short description
Doesn't matter if we use the Admin-GUI or API (client_delete_everything).
Deletion of "web" folder works.
Empty client folder (which contains symlinks) remains.
Used Version 3.1.7 p1
## correct behaviour
All Files...## short description
Doesn't matter if we use the Admin-GUI or API (client_delete_everything).
Deletion of "web" folder works.
Empty client folder (which contains symlinks) remains.
Used Version 3.1.7 p1
## correct behaviour
All Files an Folder should be deleted
## environment
Server OS: Debian
Server OS version: Stretch
ISPConfig version: 3.1.7 p1
If it might be related to the problem
```
insert the output of `nginx -v` or `apachectl -v` here
Server version: Apache/2.4.25 (Debian)
Server built: 2017-09-19T18:58:57
insert the output of `php -v` here
PHP 7.0.19-1 (cli) (built: May 11 2017 14:04:47) ( NTS )
## 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)
```3.1.11Till BrehmTill Brehmhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4864Wrong/incomplete config for Python-enabled sites2018-01-11T13:21:45ZDiego ZuccatoWrong/incomplete config for Python-enabled sites## short description
I think I've hit a bug with the first python site I tried to create :(
I created it as usual, but instead of enabling PHP I enabled python.
Then, I placed a simple test .py file in site's web/ , but trying to access...## short description
I think I've hit a bug with the first python site I tried to create :(
I created it as usual, but instead of enabling PHP I enabled python.
Then, I placed a simple test .py file in site's web/ , but trying to access it resulted in a download of the file instead of its execution.
## correct behaviour
The file should be executed and its output returned as page contents.
## environment
Server OS: Debian
Server OS version: 9
ISPConfig version: 3.1.8
## proposed fix
I manually fixed changing
```
<Directory /var/www/clients/clientXX/webYY/web>
```
to
```
<Directory /var/www/DNS.ADDRESS.OF.SITE/web>
```
Then I "automated" it adding a snippet with {DOCROOT} instead of DNS.ADDRESS.OF.SITE, but I think ISPC should do it automatically...
PS: the same bug could be with webdav, too, but I didn't test it.
## references
https://www.howtoforge.com/community/threads/bug-enabling-python-in-ispc-3-1-8p1.77873/
## screenshots
## log entries3.1.11Till BrehmTill Brehmhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4863URL Redirect doesn't accept #anchors2018-01-11T13:17:55ZDominikURL Redirect doesn't accept #anchorsIf you want to redirect a domain to another URL but including an anchor like:
http://www.domain.de#anchor
ISPConfig throws an error message:
"Invalid redirect path. Valid redirects are for example: /test/ or http://www.domain.tld/test/"...If you want to redirect a domain to another URL but including an anchor like:
http://www.domain.de#anchor
ISPConfig throws an error message:
"Invalid redirect path. Valid redirects are for example: /test/ or http://www.domain.tld/test/"
Usecase is a singlepage-Webpage where Navigation is done via anchors and if you want to directly navigate there. I already tested: apache allows that as a redirect. I don't know what about nginx - but I cant imagine that it doesn't work there?!?3.1.11Till BrehmTill Brehmhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4855Modifying certificates affects to the same domain-named sites on all servers.2018-01-11T13:21:33ZJanne MustonenModifying certificates affects to the same domain-named sites on all servers.## short description
Deleting or creating SSH-certificate to one server, affects to the same domain-named sites on other servers.
## correct behaviour
Modifying certificates should only affect to the server which the site is located.
#...## short description
Deleting or creating SSH-certificate to one server, affects to the same domain-named sites on other servers.
## correct behaviour
Modifying certificates should only affect to the server which the site is located.
## environment
Server OS: Any
ISPConfig version: (3.1.8.p1)
Related to the query
UPDATE web_domain SET ssl_request = '', ssl_cert = '' WHERE domain = 'nameofthedomain.com'
## proposed fix
Add server_id to the update query.3.1.11Till BrehmTill Brehmhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4721Wrong permissions when renaming shell user2018-01-11T13:17:22ZChristianWrong permissions when renaming shell userIf you create a shell user for a specific website the `/var/www/clients/clientXX/webXX/home/USERNAME` directory gets the correct permissions (chmod: 750, user: webXX, group: clientXX).
But when you rename the username via ISPConfig, the...If you create a shell user for a specific website the `/var/www/clients/clientXX/webXX/home/USERNAME` directory gets the correct permissions (chmod: 750, user: webXX, group: clientXX).
But when you rename the username via ISPConfig, the new created dir `/var/www/clients/clientXX/webXX/home/NEWUSERNAME` has the wrong permissions (chmod: 755, user: root, group: root). ISPConfig should set the same permissions as if it is creating a new user.3.1.11https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4077Allow customer to specify subfolder as docroot2020-07-10T11:20:04ZFloAllow customer to specify subfolder as docrootThis has been asked several times before and still is only partly answered since.
The option to change the docroot to a clean subfolder is necessary for a lot of applications to run properly ([Zend Framework as mentioned here](https:/...This has been asked several times before and still is only partly answered since.
The option to change the docroot to a clean subfolder is necessary for a lot of applications to run properly ([Zend Framework as mentioned here](https://www.howtoforge.com/community/threads/change-document-root-for-a-single-website-to-accomodate-zend-framework.48279/) or [Bedrock](https://github.com/roots/bedrock) to name some examples). Additionally this makes deployments a lot easier in some cases as you can clone your repo into a subdirectory and deploy by pulling the master branch.
- This feature was requested the first time in issue #1528 5 years ago and was scheduled for 3.0.3.3.
- 4 years ago issue #2150 was opened with a similar request and was again scheduled - this time for 3.0.4.6
- In #2529 the same request was made and scheduled for 3.0.5.1 - 3 years ago
- A similar issue is #3584 where the requested behaviour was [partly implemented with a rather simple patch](http://pastebin.com/uyjSzWEd)
- Issue #3957 requested this again 2 months ago.
Why am i opening a new issue?
I want to emphasize that this feature is very important and a lot of users have been waiting for this for a long time. Especially when looking at the forums over at howtoforge.com you can see that this question has been asked again and again and again but still there is no good solution for this.
I know that with Apache you can have multiple docroot definitions and this way you can use a subfolder as docroot, when configured manually but with nginx it's a different story.
I think it's apparent that we need a nice and convenient solution for this.
I suggest something like this:![Screen_Shot_2016-08-05_at_15.23.58](/uploads/95beecff3c9df93a1d28d290122fa3cd/Screen_Shot_2016-08-05_at_15.23.58.png)3.1.11https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/2529Configurable document root2018-12-15T18:15:07ZMichael FürmannConfigurable document rootPlease make the Document Root for apache and nginx configurable by textfield to a subfolder of
/var/www/domain.tld/web
Description:
By default the document root on nginx and apache is set to
/var/www/domain.tld/web
For most w...Please make the Document Root for apache and nginx configurable by textfield to a subfolder of
/var/www/domain.tld/web
Description:
By default the document root on nginx and apache is set to
/var/www/domain.tld/web
For most websites this is ok.
But if the application is built using frameworks like zend, symphony2 or Ruby on Rails the root path may differ from this.
E.g. Rails requires the document root to be set to
/var/www/domain.tld/web/public
Using apache you can just set a new Document Root in apache directives because the last one in the config file wins.
But nginx throws a config error on reload if there is more than one root path given in the config file of the website.
To handle this, the document root could be configurable to a subfolder of
/var/www/domain.tld/web
using a textfield as used for open_basedir3.1.11