Topics

1

Updates / Updating Apache to current version?

« on: August 27, 2020, 08:36:28 AM »

Currently CWP is offering Apache 2.4.41 on the page "Apache Re-Build", which has been released more than a year ago on August 14, 2019.

I'm worried about security flaws in such an old Apache version, there have been a lot of security updates since then:
https://www.apachelounge.com/Changelog-2.4.html

Is there a way to install a newer Apache manually without damaging the rest of CWP?

2

E-Mail / postfix fails to start after yesterday's update

« on: February 20, 2020, 09:43:07 AM »

Hi!

After yesterday's update:
postfix.x86_64    2:3.4.7-1.el7    cwp

Postfix fails to start here:

/bin/systemctl start postfix.service
Job for postfix.service failed because the control process exited with error code. See "systemctl status postfix.service" and "journalctl -xe" for details.

systemctl status postfix.service returns the following two errors:

Unable to create missing queue directories
Postfix integrity check failed!

After a rollback of the last yum update, it works again. Rollback via:
yum history
then check what the newest ID is, and then
yum history undo <ID>

This returned to postfix-2.10.1-7.el7.x86_64, which is quite a big version jump.
I guess that Postfix 3.4.7 requires a different configuration than Postfix-2.10.1.

Any ideas how to find out what's going wrong? The logs don't tell me what queue directories couldn't be created.

Here are the changes I made to the default postfix configuration to use procmail to filter and deliver mails:

yum install procmail
chmod g+s /usr/bin/procmail
nano /etc/postfix/main.cf
Change virtual_transport = dovecot to:
virtual_transport = virtualprocmail:dummy
virtualprocmail_destination_recipient_limit = 1

nano /etc/postfix/master.cf
#
# procmail LDA
virtualprocmail unix - n n - - pipe flags=DRXhuq user=redacteduser
  argv=/usr/bin/procmail -m E_SENDER=$sender E_RECIPIENT=$recipient ER_USER=$user ER_DOMAIN=$domain ER_DETAIL=$extension NEXTHOP=$nexthop /etc/procmailrc

nano /etc/procmailrc
SHELL=/bin/bash
LOGFILE=/var/log/procmail.log
DEFAULT=/var/vmail/${ER_DOMAIN}/${ER_USER}
MAILDIR=/var/vmail/${ER_DOMAIN}/${ER_USER}
DELIVER="/usr/lib/dovecot/deliver -d $LOGNAME"
INCLUDERC=/home/redacteduser/.procmailrc
:0 w
| $DELIVER
HOST=end_of_processing

nano /etc/postfix/virtual
support@redacted.com redacteduser

service postfix restart

3

CentOS-WebPanel GUI / Does "CWPpro Terminal" work for you?

« on: July 12, 2019, 10:26:45 AM »

When I click on the "Terminal" button at the top in CWP Pro (paid version), I get a submenu with two options:
"Simple Terminal"
"CWPpro Terminal"

"Simple Terminal" opens a terminal just fine in a new tab, without asking again for the password. However,
"CWPpro Terminal" doesn't seem to work with Chrome or Firefox:
- it asks again for the user name and password
- once I enter them, I get a black screen with a tiny (about one character) white square in the upper left corner

I have tried disabling Noscript on that tab, but that didn't make any difference.

Maybe I need to install some additional packages via yum to make this work?

4

Updates / Checking for new Apache or PHP versions via command line?

« on: March 19, 2019, 02:03:18 PM »

Is there a command to check whether there is an update of Apache and/or PHP available in CWP?

Apache:
Currently I have to go to CWPro Admin - WebServer settings - Apache Re-Build, and open the combobox there to check whether these is a new Apache version. The latest Apache is 2.3.38 since January, but CWPro only has 2.3.37 - I'm a bit concerned about security.

PHP:
Here I have to go to CWPro Admin - PHP Settings - PHP Version Switcher, and also open the combobox. PHP is up to date in CWP.

I would prefer a command line check, so I could write a cron script which warns me when a new version gets available. Checking manually every day is tiring.

5

CentOS-WebPanel Bugs / Editor saves files with Windows line breaks (cr/lf)

« on: February 28, 2019, 11:17:00 AM »

Both the editor in the simple file manager and the editor in the advanced file manager save text files with Windows line breaks (cr/lf) instead of Unix line breaks (lf). This causes problems with many services when you edit their configuration files.

The problem happens with both Firefox and Chrome on a Windows or Linux(!) client with CWP Pro running on Centos 7.6.1810 (Core).

I noticed this because Midnight Commander shows ^M at the end of each line.

Otherwise I'm very happy with CWP Pro!