CyberPanel 1.7 RC - Email Limits - SpamAssassin - CLI - Rewrite Context - Email Forwarding!

Hello Everyone!

Note: This is a release candidate, and an upgrade will not work, only perform fresh installs and run tests.

I am glad to announce that CyberPanel 1.7 RC is now ready to install and test, this brings a lot of features and bug fixes. This thread summarizes the features this update brings.

Single MySQL Instance Version

Earlier CyberPanel installs 2 MySQL instances by default. One instance of MySQL was dedicated to CyberPanel and other for normal websites. This was a good feature but requires more ram.

We now have two installation version, a user can choose (allowed to select during the installation process) according to their needs. If you choose two MySQL instance version you should be having more ram on your server.

Command Line Interface

With this upgrade, we now have most of the CyberPanel functionality available via command line interface. This can help programmers/developers to do add-ons/custom features in the language of their choice.

This also helps people who love to work with a terminal.

Read the documentation for more information regarding this feature:

https://docs.cyberpanel.net/doku.php?id=cli

Email Limits

Email limit is one of the exciting features of this update, CyberPanel now has its own email policy server listening at port 1089. With this feature, you can put hourly/monthly limit to an email account. This helps in stopping email spam in case you are handling email for your clients.

You can also enable/disable email logs. Read the documentation for more information:

SpamAssassin

We now have SpamAssassin to stop incoming email spam, read more:

Email Forwarding

Email forwarding was the most requested feature, Email Forwarding is now possible, read more at:

Virtual Enviroment

Recently we’ve had some issues with yum updates, however, CyberPanel will now run inside its own virtual environment, which ensures that any system-wide package upgrades do not effect CyberPanel.

Rewrite Rules

This is one of the most notable and important changes regarding rewrite rules from Apache to OpenLiteSpeed. Earlier it was very difficult for end users to convert rewrite rules from Apache to OpenLiteSpeed even though the difference was very slight.

However, with slight configuration changes (end user need not do anything on their end), you can now directly copy your Apache rules to CyberPanel rewrite rules box, without needed to change your rewrite rules.

That’s a big relief. :slight_smile:

File Manager

Earlier File Manager had some limitation, if you have read an earlier thread, you should know that you can not use catch-all rewrite rule (will disrupt the functionality of CyberPanel). However, you can now use any sort of rewrite rules and this will not disrupt the functionality of File Manager.

Display Errors

Earlier when you enable display errors for PHP, File Manager stopped working, which has also been fixed with this update.

Upload Limit

Upload limit for File Manager is now globally set to 200MB irrespective of your local PHP upload limit.

OpenLiteSpeed 1.4.33

OpenLiteSpeed 1.4.33 is also released with new features and bug fixes, read more at https://openlitespeed.org/release-log/version-1-4-x/

Installation

Install using the below command:

sh <(curl https://mirror.cyberpanel.net/install-test.sh || wget -O - https://mirror.cyberpanel.net/install-test.sh)`

Upgrade

There is beta-upgrade script available for people wanting to convert from 1.6.x to 1.7.x

Run this script and you should be successfully upgraded to 1.7, since this is a beta upgrade, if you find any issues please report below:

rm -f upgrade.py
wget https://cyberpanel.net/upgrade.py
python upgrade.py

Don’t forget to clear your browser cache after successful upgrade.

I got version 1.6 installed, Can I upgrade to this later?

Single MySQL Instance Version Earlier CyberPanel installs 2 MySQL instances by default. One instance of MySQL was dedicated to CyberPanel and other for normal websites. This was a good feature but requires more ram.

We now have two installation version, a user can choose (allowed to select during the installation process) according to their needs. If you choose two MySQL instance version you should be having more ram on your server.

I got version 1.6 installed, Can I upgrade to this later?
Single MySQL Instance Version Earlier CyberPanel installs 2 MySQL instances by default. One instance of MySQL was dedicated to CyberPanel and other for normal websites. This was a good feature but requires more ram.

We now have two installation version, a user can choose (allowed to select during the installation process) according to their needs. If you choose two MySQL instance version you should be having more ram on your server.

You can upgrade to 1.7 later, but for single instance version, you need to do a fresh install.

Installing this version now, and I selected single database instance & MariaDB 10.3 (menu 4), and it is now supported by Cyberpanel?

Installing this version now, and I selected single database instance & MariaDB 10.3 (menu 4), and it is now supported by Cyberpanel?

Yes.

hi together

how can i install this test version if i am running 1.6.4 right now ? If i try it using the command ant the end of this thread it says u already installed Cyberpanel in the installer.

hi together

how can i install this test version if i am running 1.6.4 right now ? If i try it using the command ant the end of this thread it says u already installed Cyberpanel in the installer.

This is a release candidate, and an upgrade will not work, only perform fresh installs and run tests.

But if you still want to run this in production you can download from https://cyberpanel.net/CyberPanelTemp.tar.gz

The further process is similar to How to manually upgrade/downgrade CyberPanel! — CyberPanel - WebHosting Control Panel for OpenLiteSpeed

hi together

how can i install this test version if i am running 1.6.4 right now ? If i try it using the command ant the end of this thread it says u already installed Cyberpanel in the installer.

This is a release candidate, and an upgrade will not work, only perform fresh installs and run tests.

But if you still want to run this in production you can download from https://cyberpanel.net/CyberPanelTemp.tar.gz

The further process is similar to How to manually upgrade/downgrade CyberPanel! — CyberPanel - WebHosting Control Panel for OpenLiteSpeed

okay thanks

bug:
CentOs 7.5 last (with update)
Clean install, one database, mariadb 10.3;

bug: CentOs 7.5 last (with update) Clean install, one database, mariadb 10.3;

Going to run tests.

Thanks for for your hard work… Will test this rc version too :slight_smile:

Thanks for for your hard work... Will test this rc version too :)

Feel free to report any bugs. :slight_smile:

Hi,
After doing update, I got a 503 error.

Traceback (most recent call last):
File “manage.py”, line 22, in
execute_from_command_line(sys.argv)
File “/usr/lib64/python2.7/site-packages/django/core/management/init.py”, line 363, in execute_from_command_line
utility.execute()
File “/usr/lib64/python2.7/site-packages/django/core/management/init.py”, line 337, in execute
django.setup()
File “/usr/lib64/python2.7/site-packages/django/init.py”, line 27, in setup
apps.populate(settings.INSTALLED_APPS)
File “/usr/lib64/python2.7/site-packages/django/apps/registry.py”, line 85, in populate
app_config = AppConfig.create(entry)
File “/usr/lib64/python2.7/site-packages/django/apps/config.py”, line 94, in create
module = import_module(entry)
File “/usr/lib64/python2.7/importlib/init.py”, line 37, in import_module
import(name)
ImportError: No module named emailPremiumemailPremiumemailPremiumemailPremiumemailPremiumemailPremium
Traceback (most recent call last):
File “upgradeBeta.py”, line 462, in
Upgrade.upgrade()
File “upgradeBeta.py”, line 391, in upgrade
res = subprocess.check_output(command, shell=True)
File “/usr/lib64/python2.7/subprocess.py”, line 575, in check_output
raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command ‘echo ‘ALTER TABLE e_forwardings DROP PRIMARY KEY;ALTER TABLE e_forwardings ADD id INT AUTO_INCREMENT PRIMARY KEY;’ | python manage.py dbshell’ returned non-zero exit status 1

Hi, After doing update, I got a 503 error.

Traceback (most recent call last):
File “manage.py”, line 22, in
execute_from_command_line(sys.argv)
File “/usr/lib64/python2.7/site-packages/django/core/management/init.py”, line 363, in execute_from_command_line
utility.execute()
File “/usr/lib64/python2.7/site-packages/django/core/management/init.py”, line 337, in execute
django.setup()
File “/usr/lib64/python2.7/site-packages/django/init.py”, line 27, in setup
apps.populate(settings.INSTALLED_APPS)
File “/usr/lib64/python2.7/site-packages/django/apps/registry.py”, line 85, in populate
app_config = AppConfig.create(entry)
File “/usr/lib64/python2.7/site-packages/django/apps/config.py”, line 94, in create
module = import_module(entry)
File “/usr/lib64/python2.7/importlib/init.py”, line 37, in import_module
import(name)
ImportError: No module named emailPremiumemailPremiumemailPremiumemailPremiumemailPremiumemailPremium
Traceback (most recent call last):
File “upgradeBeta.py”, line 462, in
Upgrade.upgrade()
File “upgradeBeta.py”, line 391, in upgrade
res = subprocess.check_output(command, shell=True)
File “/usr/lib64/python2.7/subprocess.py”, line 575, in check_output
raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command ‘echo ‘ALTER TABLE e_forwardings DROP PRIMARY KEY;ALTER TABLE e_forwardings ADD id INT AUTO_INCREMENT PRIMARY KEY;’ | python manage.py dbshell’ returned non-zero exit status 1

Thank you!

https://docs.cyberpanel.net/doku.php?id=upgrade

After all, I reinstalled.
I still want to spread it because there are few users in Japan.

Thank you!
https://docs.cyberpanel.net/doku.php?id=upgrade

After all, I reinstalled.
I still want to spread it because there are few users in Japan.

thank you.

Sory, solved :slight_smile:
@usmannasir any suggestion?

Sory, solved :) @usmannasir any suggestion?

Sorry?

how to uninstall spamassassin CP1.7 ?

how to uninstall spamassassin CP1.7 ?

yum remove spamassassin -y

Then open:

/etc/postfix/master.cf

Remove

-o content_filter=spamassassin

and

spamassassin unix - n n - - pipe flags=R user=spamd argv=/usr/bin/spamc -e /usr/sbin/sendmail -oi -f ${sender} ${recipient}