ISPConfig 3 issueshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues2022-12-05T17:02:25Zhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6339Issue on managing aliases in a multiserver environment2022-12-05T17:02:25ZLorenzo ValoriIssue on managing aliases in a multiserver environment## Summary
If you change the parent domain on an alias with another site hosted on a different server than the initial one, the configuration will be correctly done on the new server but the alias will not be removed from the old server
...## Summary
If you change the parent domain on an alias with another site hosted on a different server than the initial one, the configuration will be correctly done on the new server but the alias will not be removed from the old server
## Steps to reproduce
1. create a website alias (e.g. dev.example.com) and assign it to a site hosted on server A (e.g. example.com)
2. enter in the alias you just created (dev.example.com) and change the assignment to another site hosted on server B (e.g. example.it)
3. now dev.example.com will be correctly configured on server B but will not be removed from the vhost on server A example.com, it will still result in the apache configuration and the a DB record on server A will also remain
## Correct behaviour
The alias configuration should be completely removed from server A and carried over to server B
## Environment
Server OS + version: Ubuntu 18.04.6 LTS
ISPConfig version: 3.2.8p1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6384main.cf get overwritten if i change "Backup is mount" in Config->Server2022-12-05T17:02:02ZHannesmain.cf get overwritten if i change "Backup is mount" in Config->ServerHi,
If i turn on (or off) the "Backup is a mount" option than the main.cf are changed (think with postconf) but the postfix_custom.conf.master custom directives are ignored.
In my case the smtpd_sender_restrictions=... are overwritten t...Hi,
If i turn on (or off) the "Backup is a mount" option than the main.cf are changed (think with postconf) but the postfix_custom.conf.master custom directives are ignored.
In my case the smtpd_sender_restrictions=... are overwritten to the default one from ispconfig (my postfix.custom.conf.master works with ispconfig_update but get ignored here)
Maybe a big warning if a important config file gets changes (like main.cf or dovecot.conf...) would be nice.
Thankshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6273_getinitcommand init script symlinks broken2022-12-05T17:01:51ZChristian_getinitcommand init script symlinks brokenon my gentoo system i'm using symlinks for php-fpm init scripts.
```
/etc/init.d/php-fpm-php7.4 -> /etc/init.d/php-fpm
/etc/init.d/php-fpm-php7.3 -> /etc/init.d/php-fpm
```
```
file system.inc.php
function _getinitcommand
$full_init_scr...on my gentoo system i'm using symlinks for php-fpm init scripts.
```
/etc/init.d/php-fpm-php7.4 -> /etc/init.d/php-fpm
/etc/init.d/php-fpm-php7.3 -> /etc/init.d/php-fpm
```
```
file system.inc.php
function _getinitcommand
$full_init_script_path = realpath($init_script_directory.'/'.$servicename);
```
realpath() changes /etc/init.d/php-fpm-php7.4 to /etc/init.d/php-fpm which breaks reload and restart commands.
why is realpath() there? can this be adjusted in any way?
my workaround so far:
```
if(is_link($init_script_directory.'/'.$servicename)) {
$full_init_script_path = $init_script_directory.'/'.$servicename;
}
else {
$full_init_script_path = realpath($init_script_directory.'/'.$servicename);
}
```https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6354Rewrite to HTTPs doesn't work for aliasdomains (Apache)2022-12-05T17:01:26ZDominikRewrite to HTTPs doesn't work for aliasdomains (Apache)
## Summary
Rewrite HTTP to HTTPS doesn't work for aliasdomains with own redirect rules (e.g. subdirectory) in Apache
## Steps to reproduce
1. Setup a website and an aliasdomain for it
2. Set this aliasdomain redirecting to any subdirec...
## Summary
Rewrite HTTP to HTTPS doesn't work for aliasdomains with own redirect rules (e.g. subdirectory) in Apache
## Steps to reproduce
1. Setup a website and an aliasdomain for it
2. Set this aliasdomain redirecting to any subdirectory via Redirect Path...
3. Enable Rewrite HTTP to HTTPS for this website
If you open the website itself in the browser, the rediret to https works for the website itself. If you open the aliasdomain, the redirect doesn't work and stays with http.
## Correct behaviour
redirect should also work for the aliasdomain
## Suggestions
either we should add a corresponding checkbox to all alias and subdomains, to make it possible to enable https-rewrite for all domains, or we can move the https-rewrite-rule in vhost-config to the top, that it is called as the first one.
for sure both solutions mean impact - in the latter case also redirects to external URLs would be translated to https before redirected, which might be the wrong behaviour for several cases - but in my opinion this is the correct behaviour anyway... if I enable this redirect for my hole website, i would expect that it works with all domains and sudbomains. If I don't want it for all domains I can still use htaccess for the selected domains and keep it disabled for the website itself...
The option to add a checkbox to all aliasdomains seems to be inconvenient if there are many domains in a website...https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6356Email Spamfilter blacklist doesn't create .conf file2022-12-05T17:00:34ZTony GEmail Spamfilter blacklist doesn't create .conf fileIn a fully operational Postfix/Rspamd environment, go to ISPConfig Email>Spamfilter and create a whitelist record. A new .conf file is created in:
/etc/rspamd/local.d/users/spamfilter_wblist_nn.conf.
Now go to create a blacklist rec...In a fully operational Postfix/Rspamd environment, go to ISPConfig Email>Spamfilter and create a whitelist record. A new .conf file is created in:
/etc/rspamd/local.d/users/spamfilter_wblist_nn.conf.
Now go to create a blacklist record. The record is saved in the ISPConfig database but no file is created in the folder for Rspamd to use.
I've searched my system and the filters are not anywhere in the file system.
If this is expected behaviour, please note here how Rspamd uses the blacklist data without the .conf file, action info, etc.
When a whitelist record is disabled, it remains in the database but the .conf file is removed. ~~Might blacklist records simply be in the same state, disabled, even when the UI says they are enabled?~~ I checked the spamfilter_wblist table and 'B' Blacklist records are active.
More info will be provided if required.
Ubuntu 20.04
ISPConfig version: 3.2.2https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6197Use of want_spam & actions (wblist) in rspamd yields unexpected results2022-12-05T16:55:28ZZakUse of want_spam & actions (wblist) in rspamd yields unexpected results## Summary
User Block-/Allowlist config is generated with both "actions" and "want_spam" present. \
The usage of "actions" renders "want_spam" obsolete und does not honor the function that "want_spam" is supposed to provide. \
If "want_s...## Summary
User Block-/Allowlist config is generated with both "actions" and "want_spam" present. \
The usage of "actions" renders "want_spam" obsolete und does not honor the function that "want_spam" is supposed to provide. \
If "want_spam" is used rspamd is supposed to skip the evaluation of an email. The resulting config might provide the expected result because of "actions", but it still adds the "X-Spamd-Bar" header, which is unwanted behaviour because the header might be used in sieve rules and therefore should not be present (or at least present without a value) on emails that are handled by an entry in the allowlist.
## Steps to reproduce
Using the stock template (slightly modified to also match the from header):
```
spamfilter_wblist-2046 {
priority = 26;
from = "sender@domain.tld";
rcpt = "recipient@domain.tld";
want_spam = yes;
apply {
actions {
reject = null;
"add header" = null;
greylist = null;
"rewrite subject" = null;
}
}
}
spamfilter_wblist-2046.2 {
priority = 26;
mime_from = "sender@domain.tld";
rcpt = "recipient@domain.tld";
want_spam = yes;
apply {
actions {
reject = null;
"add header" = null;
greylist = null;
"rewrite subject" = null;
}
}
}
```
the following is logged by rspamd:
```
2021-07-12 11:03:46 #930(normal) <24ddc3>; task; rspamd_task_write_log: id: <CAP03e=xDdfHS_j7N=7JdzSrOc3fiXA2Efk+oumGrzZ9ugWEwHw@mail.domain.tld>, qid: <4698E3BE9D>, ip: 209.85.160.171, from: <sender@domain.tld>, (default: F (no action): [-0.51/nan] [DMARC_POLICY_ALLOW(-0.50){domain.tld;none;},R_PARTS_DIFFER(0.50){100.0%;},R_DKIM_ALLOW(-0.20){domain.tld:s=20161025;},R_SPF_ALLOW(-0.20){+ip4:209.85.128.0/17;},MIME_GOOD(-0.10){multipart/alternative;text/plain;},MX_GOOD(-0.01){},ALREADY_AV_CHECKED(0.00){},ARC_NA(0.00){},ASN(0.00){asn:15169, ipnet:209.85.128.0/17, country:US;},DKIM_TRACE(0.00){domain.tld:+;},FREEMAIL_ENVFROM(0.00){domain.tld;},FREEMAIL_FROM(0.00){domain.tld;},FROM_EQ_ENVFROM(0.00){},FROM_HAS_DN(0.00){},MID_RHS_MATCH_FROMTLD(0.00){},MIME_TRACE(0.00){0:+;1:+;2:~;},PREVIOUSLY_DELIVERED(0.00){recipient@domain.tld;},RCPT_COUNT_ONE(0.00){1;},RCVD_COUNT_TWO(0.00){2;},RCVD_TLS_ALL(0.00){},SENDER_REP_HAM(0.00){asn: 15169(-0.19), country: US(-0.00), ip: 0.0.0.0(-0.50);},TO_DN_ALL(0.00){},TO_MATCH_ENVRCPT_ALL(0.00){},USER_REJECTS_BLACKLISTED_FILES(0.00){recipient@domain.tld;}]), len: 2555, time: 775.295ms, dns req: 21, digest: <4915ae6bed441b333c191c11653f0540>, rcpts: <recipient@domain.tld>, mime_rcpts: <recipient@domain.tld>, settings_id: spamfilter_wblist-2046.2
```
## Correct behaviour
Skip evaluation of an email immediately. \
Using a config without the actions stanza
```
spamfilter_wblist-2046 {
priority = 26;
from = "sender@domain.tld";
rcpt = "recipient@domain.tld";
want_spam = yes;
}
spamfilter_wblist-2046.2 {
priority = 26;
mime_from = "sender@domain.tld";
rcpt = "recipient@domain.tld";
want_spam = yes;
}
```
the following is logged:
```
2021-07-12 11:04:44 #1587(normal) <7a17ab>; task; rspamd_task_write_log: id: <CAP03e=wRW8By+3ONS3BcpcFF=EHqP0Ja9SpDV0gBqubzt2FiMQ@mail.domain.tld>, qid: <BCD863BFA5>, ip: 209.85.219.51, from: <sender@domain.tld>, (default: S (no action): [0.00/15.00] []), len: 2548, time: 1.217ms, dns req: 0, digest: <5eb295da1042112a088cf8f7958bcbe6>, rcpts: <recipient@domain.tld>, mime_rcpts: <recipient@domain.tld>, settings_id: spamfilter_wblist-2046.2
```
Therefore the evaluation is immediately skipped.
## Environment
OS: irrelevant \
ISPConfig up to 3.2.5.
## Proposed fix
Remove "actions from the "rspamd_wblist.inc.conf.master" template. \
(And add a second entry to match the "From header" - I already proposed that in #5419)https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5932When update ISPConfig, if a custom port is setted for apps domain it returns ...2022-12-03T23:05:07ZSergioWhen update ISPConfig, if a custom port is setted for apps domain it returns to the default 8081, only on the config file (remains custom on the web panel)## short description
When updating ISPConfig if App Domain have a non standard value it come back on the default 8081 even if the Web Panel reports the custom port.
## correct behaviour
App domain should remain on the custom port as set...## short description
When updating ISPConfig if App Domain have a non standard value it come back on the default 8081 even if the Web Panel reports the custom port.
## correct behaviour
App domain should remain on the custom port as setted on the web panel.
## environment
Server OS: Ubuntu
Server OS version: 20.04.01
ISPConfig version: <= 3.2.1https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6408Import of language files fails without error2022-11-07T14:58:16ZTill BrehmImport of language files fails without errorSee: https://forum.howtoforge.com/threads/unable-to-import-languagefile.89704/See: https://forum.howtoforge.com/threads/unable-to-import-languagefile.89704/Till BrehmTill Brehmhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6396Crons not updated when changing cron limit2022-10-24T17:01:23ZThomCrons not updated when changing cron limit<!-- Before creating a bug report, please:
- Read the contribution guidelines: https://git.ispconfig.org/ispconfig/ispconfig3/-/blob/develop/CONTRIBUTING.md
- Do not ask support questions here. If you are unsure if your problem is a bug,...<!-- Before creating a bug report, please:
- Read the contribution guidelines: https://git.ispconfig.org/ispconfig/ispconfig3/-/blob/develop/CONTRIBUTING.md
- Do not ask support questions here. If you are unsure if your problem is a bug, post a thread on the forum: https://www.howtoforge.com/community/#ispconfig-3.23
- Make sure to remove any content from the description that you did not add. For example, if there are no related log entries, remove the whole "Related log entries" part.
-->
## Summary
<!-- What is happening and what is wrong with that? -->
When changing the cronjob level (URL/chrooted/full) in the client limits, crons are not updated.
## Correct behaviour
<!-- What should happen instead? -->
The crons should be updated (e.g. when switching from full to chrooted all should become chrooted crons)
## Environment
Server OS + version: Debian 11 \
ISPConfig version: 3.2.8p1
<!-- _you can use `grep 'ISPC_APP_VERSION' /usr/local/ispconfig/server/lib/config.inc.php` to get it from the command line_ -->
Software version of the related software:
<!-- You can use 'nginx -v' or 'apachectl -v' to find the webserver version. Use 'php -v' to find the PHP version.> Put this in code blocks, like so: -->https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6024change shell user Base Dir creates warning2022-09-25T19:19:23ZJesse Norellchange shell user Base Dir creates warningWhen changing the shell user Base dir, in my case from /var/www/clients/client1/web20 to /var/www/clients/client1/web20/blah, I see this error:
```
21.01.2021-13:08 - DEBUG - Calling function 'update' from plugin 'shelluser_base_plugin' ...When changing the shell user Base dir, in my case from /var/www/clients/client1/web20 to /var/www/clients/client1/web20/blah, I see this error:
```
21.01.2021-13:08 - DEBUG - Calling function 'update' from plugin 'shelluser_base_plugin' raised by event 'shell_user_update'.
21.01.2021-13:08 - DEBUG - Homedir New: /var/www/clients/client1/web20/blah
21.01.2021-13:08 - DEBUG - Homedir Old: /var/www/clients/client1/web20
21.01.2021-13:08 - DEBUG - safe_exec cmd: chattr -i '/var/www/clients/client1/web20' - return code: 0
PHP Warning: rename(/var/www/clients/client1/web20,/var/www/clients/client1/web20/blah): Invalid argument in /usr/local/ispconfig/server/lib/classes/
system.inc.php on line 894
```
(From https://www.howtoforge.com/community/threads/the-following-changes-are-not-yet-populated-to-all-servers.86171/#post-416503)Jesse NorellJesse Norellhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6376PHP version settings do not get mirrored2022-08-31T07:16:57ZTill BrehmPHP version settings do not get mirroredhttps://forum.howtoforge.com/threads/server1-and-server2-not-using-the-same-php-version.89331/https://forum.howtoforge.com/threads/server1-and-server2-not-using-the-same-php-version.89331/https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6368Spamfilter whitelist email field render in list doesn't match actual data2022-07-26T20:01:02ZTony GSpamfilter whitelist email field render in list doesn't match actual dataRef #6367 for context about using Regex in the spamfilter whitelist From field.
For this issue, enter the following Regex
```(.*\.)*creepers.org```
This is how it appears in the list of whitelist records:
![image](/uploads/0493cdac48...Ref #6367 for context about using Regex in the spamfilter whitelist From field.
For this issue, enter the following Regex
```(.*\.)*creepers.org```
This is how it appears in the list of whitelist records:
![image](/uploads/0493cdac48b72c94b311069772ba50eb/image.png)
Note the escaping slash on the period/fullstop is not rendered. It's not removed from the data, it's just not rendered in the list page.
Note also, that contrary to 6367, in this case the leading '@' is not applied. That's good, but I'm not sure what condition triggers the prefix of that character.
I will look at the code for this trivial rendering issue, and for 6367, and see if I can coordinate patches with @jnorell if he's working in this area.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6360An IDN is not accepted for Destination Email in Email Forward add form.2022-07-10T08:38:26ZEdAn IDN is not accepted for Destination Email in Email Forward add form.
## Summary
An IDN is not accepted for Destination Email in Email Forward add form. Punycode must be used. the displayed error is: The destination contains at least one invalid email address
## Steps to reproduce
1. add an IDN (i.e. cu...
## Summary
An IDN is not accepted for Destination Email in Email Forward add form. Punycode must be used. the displayed error is: The destination contains at least one invalid email address
## Steps to reproduce
1. add an IDN (i.e. cuvée.com) as destination email in email forward form - produces error
## Correct behaviour
it should be allowed as it is everywhere else on IspConfig3 latest, patched.
## Environment
Server OS + version: Debian 10 and Debain 11
ISPConfig version: 3.2.8p1
Software version of the related software:
Apache 2.4.53
7.4.30https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6104Creating DNS secondary zone fails if name has ÅÄÖ characters and name without...2022-06-17T12:51:22ZTapio LehtonenCreating DNS secondary zone fails if name has ÅÄÖ characters and name without umlauts exists## short description
Trying to create DNS secondary zone for a zone where zone name has non ASCII characters fails. Looks like if there is zone name with Ö replaced by O or Ä replaced by A adding fails with error
There is already a reco...## short description
Trying to create DNS secondary zone for a zone where zone name has non ASCII characters fails. Looks like if there is zone name with Ö replaced by O or Ä replaced by A adding fails with error
There is already a record for this zone.
## correct behaviour
It should work so also those zones get secondary.
Example: I have primary zone hääyöaie.fi. Adding secondary for that works.
I remove the secondary zone, create new primary zone haayoaie.fi, create secondary zone fo haayoaie.fi. Now creating secondary zone for hääyöaie.fi fails with error "There is already a record for this zone."
How to work around the bug: Create the secondary zone where name has ÅÄÖ characters first. Then adding secondary zone with umlauts removed works.
I'm guessing ISPConfig checks for existing secondary zone by removing umlauts. It does not add umlauts when checking so changing order of creating secondary zones helps
## environment
root@posti:~# cat /etc/debian_version
10.8
ISPConfig 3.2.2
If it might be related to the problem
```
insert the output of `nginx -v` or `apachectl -v` here
root@posti:~# apachectl -v
Server version: Apache/2.4.38 (Debian)
Server built: 2020-08-25T20:08:29
```
```
insert the output of `php -v` here
root@posti:~# php -v
PHP 7.3.27-9+0~20210227.82+debian10~1.gbpa4a3d6 (cli) (built: Feb 27 2021 15:50:50) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.27, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.27-9+0~20210227.82+debian10~1.gbpa4a3d6, Copyright (c) 1999-2018, by Zend Technologies
root@posti:~#
```https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6351Website redirect target with hashtag #2022-06-17T11:16:27ZJulianWebsite redirect target with hashtag #If the redirect target contains a hashtag, the rewrite option NE is required else the hashtag gets url encoded.
does not work:
![grafik](/uploads/681b5443a245e770527f21d5327145d1/grafik.png)
works:
![grafik](/uploads/058501190375edc0...If the redirect target contains a hashtag, the rewrite option NE is required else the hashtag gets url encoded.
does not work:
![grafik](/uploads/681b5443a245e770527f21d5327145d1/grafik.png)
works:
![grafik](/uploads/058501190375edc038f8a062bde2fb38/grafik.png)https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6087Apache vhost config invalid when using redirect: proxy and to-https2022-06-17T11:16:13ZPetr MifekApache vhost config invalid when using redirect: proxy and to-https## short description
Using both Redirect Type: proxy and Rewrite HTTP to HTTPS with Apache results in invalid configuration - Apache returns status 500. Site is configured on server with Apache and SSL with Letsencrypt enabled.
## corre...## short description
Using both Redirect Type: proxy and Rewrite HTTP to HTTPS with Apache results in invalid configuration - Apache returns status 500. Site is configured on server with Apache and SSL with Letsencrypt enabled.
## correct behaviour
The request should be handled with a rewrite to HTTPS and then proxied.
```
# Generated (faulting) config snippet (Apache non-ssl part of the config):
RewriteEngine on
RewriteCond %{REQUEST_URI} ^/\.well-known/acme-challenge/
RewriteRule ^ - [END]
RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
RewriteRule ^/(.*)$ http://1.2.3.4/$1 [proxy]
RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]
RewriteRule ^/(.*)$ http://1.2.3.4/$1 [proxy]
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L,NE]
```
```
# Updated (working) config snippet (Apache non-ssl part of the config):
RewriteEngine on
RewriteCond %{REQUEST_URI} ^/\.well-known/acme-challenge/
RewriteRule ^ - [END]
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L,NE]
RewriteCond %{HTTP_HOST} ^example\.com$ [NC]
RewriteRule ^/(.*)$ http://1.2.3.4/$1 [proxy]
RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]
RewriteRule ^/(.*)$ http://1.2.3.4/$1 [proxy]
```
## environment
Server OS: debian
Server OS version: buster
ISPConfig version: 3.2.2/nightly
## proposed fix
Move the HTTP-to-HTTPS rewrite up just after the acme challenge exemption:
Patch:
```
--- ispconfig/server/conf/vhost.conf.master 2021-03-04 01:17:38.371357346 +0000
+++ ispconfig/server/conf/vhost.conf.master.fix_tossl_and_proxy 2021-03-04 01:16:47.113325799 +0000
@@ -493,6 +493,15 @@
RewriteCond %{REQUEST_URI} ^/\.well-known/acme-challenge/
RewriteRule ^ - [END]
</tmpl_if>
+<tmpl_if name='ssl_enabled'>
+<tmpl_else>
+<tmpl_if name='rewrite_to_https' op='==' value='y'>
+ RewriteCond %{HTTPS} off
+ <tmpl_if name='apache_version' op='<' value='2.4' format='version'>RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/
+</tmpl_if>
+ RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L,NE]
+</tmpl_if>
+</tmpl_if>
<tmpl_if name='seo_redirect_enabled'>
RewriteCond %{HTTP_HOST} <tmpl_var name='seo_redirect_operator'>^<tmpl_var name='seo_redirect_origin_domain'>$ [NC]
<tmpl_if name='apache_version' op='<' value='2.4' format='version'>
@@ -521,15 +530,6 @@
RewriteRule ^/(.*)$ <tmpl_var name='rewrite_target'><tmpl_if name="rewrite_add_path" op="==" value="y">$1</tmpl_if> <tmpl_var name='rewrite_type'>
</tmpl_loop>
-<tmpl_if name='ssl_enabled'>
-<tmpl_else>
-<tmpl_if name='rewrite_to_https' op='==' value='y'>
- RewriteCond %{HTTPS} off
- <tmpl_if name='apache_version' op='<' value='2.4' format='version'>RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/
-</tmpl_if>
- RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L,NE]
-</tmpl_if>
-</tmpl_if>
</tmpl_if>
# add support for apache mpm_itk
```
## screenshots
![ApacheRedirProxyAndHttpsResultsInStatus500](/uploads/578e36743df07352654ae7c2d349250c/ApacheRedirProxyAndHttpsResultsInStatus500.jpg)https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6352CentOS 8 / Almalinux 8 mailman - unkonwn user in virtual mailbox table + mail...2022-06-17T09:21:08ZPacoCentOS 8 / Almalinux 8 mailman - unkonwn user in virtual mailbox table + mailman.conf for httpdI post that issue here, firstly posted in forum:
https://www.howtoforge.com/community/threads/centos-8-almalinux-8-mailman-unkonwn-user-in-virtual-mailbox-table.89076/
I found a solution and post it on forum and I'll be happy if you im...I post that issue here, firstly posted in forum:
https://www.howtoforge.com/community/threads/centos-8-almalinux-8-mailman-unkonwn-user-in-virtual-mailbox-table.89076/
I found a solution and post it on forum and I'll be happy if you implement that in next version of ispconfig and update centos 8 and/or create a new perfect server tutorial for AlmaLinux 8.PacoPacohttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/4349Disabled PHP and awstats selected2022-05-31T20:46:00ZenavnDisabled PHP and awstats selectedWhen PHP is disabled and awstats is selected, stats doesn't work.
As i see it there is 2 ways to fix this
* Create a conf file that insures that there at least is enabled modphp
* Edit vhost template to have special condition for when...When PHP is disabled and awstats is selected, stats doesn't work.
As i see it there is 2 ways to fix this
* Create a conf file that insures that there at least is enabled modphp
* Edit vhost template to have special condition for when php is disabled
Any pros/cons or other ideas?https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6348Apps Vhost blocked from using PHP after saving changes in ISPConfig2022-05-28T09:07:50ZAlex JohnsonApps Vhost blocked from using PHP after saving changes in ISPConfig## Summary
File in question: /etc/apache2/sites-enabled/000-apps.vhost
Apps.vhost is modified after saving on a fresh ISPConfig system as below, removing the ability to use PHP apps (phpmyadmin, etc) after the save.
Saving changes und...## Summary
File in question: /etc/apache2/sites-enabled/000-apps.vhost
Apps.vhost is modified after saving on a fresh ISPConfig system as below, removing the ability to use PHP apps (phpmyadmin, etc) after the save.
Saving changes under System Server Config > Server Name > Web > Apps VHost causes ISPConfig to pull from the conf master file. This file is not the same as a fresh installed ISPConfig.
Occurs on both Debian and Ubuntu systems, installed using: https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/
## Steps to reproduce
Active File: /etc/apache2/sites-enabled/000-apps.vhost
On the fresh install, without touching ISPConfig yet, the apps vhost has the following under ServerAdmin line (around line 9):
<Directory /var/www/apps>
<FilesMatch "\.ph(p3?|tml)$">
SetHandler None
</FilesMatch>
</Directory>
Inactive File: /usr/local/ispconfig/server/conf-custom/apache_apps.vhost.master
Conf directory apps vhost, same location as above:
<FilesMatch "\.ph(p3?|tml)$">
SetHandler None
</FilesMatch>
Without the directory line in there, all PHP is disabled.
## Correct behaviour
The conf directory file should contain the directory statements in /usr/local/ispconfig/server/conf-custom/apache_apps.vhost.master
## Environment
Many OS & versions, effects any server I install using this tutorial: https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/
## Proposed fix
Correct conf directory file as listed abovehttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6132dns: better cname checks2022-05-09T17:33:41ZJesse Norelldns: better cname checksNeed to implement more/better checking for CNAME records to prevent invalid records. Eg. not long ago someone reported an issue which was caused by creating CAA records for a hostname which had a CNAME records. Just now I created a CNA...Need to implement more/better checking for CNAME records to prevent invalid records. Eg. not long ago someone reported an issue which was caused by creating CAA records for a hostname which had a CNAME records. Just now I created a CNAME record for a hostname which already had a TXT record, which is invalid. We should look up the exact set of what is allowed to be present with CNAME and only allow those.