Community
Upgraded from version 1.8 build 4 to version 1.8 build 5. But there’s some issues,
I will update this post if I find more issues ASAP!
:8090/serverstatus/services
error: Could not connect to server. Please refresh this page.
powerdns
journalctl -f | grep pdns
error: Could not retrieve security status update for ‘4.1.1-1.Ubuntu’ on ‘auth-4.1.1-1.Ubuntu.security-status.secpoll.powerdns.com.’, RCODE = Non-Existent domain
Please let me know when all these issues are fixed because I am experiencing them as well after I upgraded.
Please let me know when all these issues are fixed because I am experiencing them as well after I upgraded.
Sure! Lets hope these issues gets fixed ASAP! 
ubuntu or centos ?
@Altunkurt said:
ubuntu or centos ?
CentOS
CentOs is fixed now, you just need to run the upgrade as listed here
If using Ubuntu do the same as above, then run Ubuntu update. (apt-get update && apt-get upgrade) if services are still not working.
Worked for two installations of mine. Ubuntu did not work until new updates got added
@bsanz16 said:
CentOs is fixed now, you just need to run the upgrade as listed here
02 - Upgrading CyberPanel - 01 - Install/Upgrade - CyberPanel CommunityIf using Ubuntu do the same as above, then run Ubuntu update. (apt-get update && apt-get upgrade) if services are still not working.
Worked for two installations of mine. Ubuntu did not work until new updates got added
Is it really fixed? I know the update part, been using CyberPanel for 1+ years. Then again why CyberPanel team didn’t post an update about it if it’s really fixed? Let’s try upgrading and see what happens.
@bsanz16 just upgraded it again. Nothing is fixed. 1-4 all probs are there.
Are you on centos or ubuntu?
@bsanz16 said:
Are you on centos or ubuntu?
CentOS
try run yum update, my centos worked straight away once updated again on 1.8.5
Ubuntu I downgraded to 1.8.4 then upgrade to 1.8.5 then 1.8.5 again after service status got fixed
See this thread for note about fixed, 3 up from bottom
check powerdns version, it should be 4.2 on 1.8.5 It may not have been updated even though you do not use
run this in ssh
pdns_control version
@bsanz16 bro! All of my services are okay! I can restart or pause any service through panel! My only issues are these,
@bsanz16 and yes pdns version is 4.2
@bsanz16 also to clarify more, all of my websites are working and all are up. Just those issues are my only concern that’s all.
if you didn’t try it update mysql/mariadb that is all I can think of.
@bsanz16 all of my system software is up to date. I update CentOS 3-5 times a day. No software is outdated. Also I use MariaDB 10.3
@bsanz16 if it helps to narrow down the issue, I use dedicated server, no VPS/ VDS etc.
@bsanz16 if I am not wrong, issue 1-3 is more likely a “typo”. For issue 4 that is another case. @CyberPanel needs to dig more to gain what that issue is. Who knows maybe that’s also a “typo” sort of issue or any integration related issue.
You can check #2 by logging into phpmyadmin as root mysql and password and look in Cyberpanel database under loginSystem_administrator`user, first and last name is in there.
Issue 2 and 3 data is present, not deleted or lost but isn’t showing. Just blank. If I try to edit profile, first and last name is present but that isn’t showing in the panel.
Hi!
I just registered because I’ve been having some problems after I upgraded to 1.8.5 a few days ago. At first I thought something wrong was happening with my SSL certifications, maybe I had hit the limit in that week, but then I tried to create an email address for a domain, and this error showed up:
Cannot create email account. Error message: 0,(1054, “Unknown column ‘mail’ in ‘field list’”)s
I went to check if the field name was there, and it is there but it is called “email” not ‘mail’
and I am getting the powerDNS issue:
Error message: (1054, “Unknown column ‘masterServer’ in ‘field list’”)
I am running a Ubuntu 18.04 droplet at digitalocean.com. So my problems are with SSL, not being able to create new certificates from the control panel, can’t create emails and the powerdns thing.
Also, I did all the recommended steps above, the apt update && apt upgrade.
The 1054 error seems to be related to mysql / mariadb and could possibly be the cause of all the issues being the database tables have not updated correctly on the upgrade.
You could try take a backup and then run a check / repair databases in root mysql that’s if you have not already tried to fix this way.
Shared MariaDB/MySQL error codes
1054 42S22 ER_BAD_FIELD_ERROR Unknown column ‘%s’ in ‘%s’
Another option if you have updated mariadb to 10.2 or above rollback to 10.1 (after making a backup) and run cyberpanel update again. then if all good update the version.
I am not a cyberpanel expert or programmer, just offering suggestions to try help 
Hi, I have another issue added to those of minhazulOO7.
After upgrade all the emails password don’t work. To correct it, I had to change the passwords of each email 
This should be fixed with new upgrade code that is pushed today.
@CyberPanel said:
- Still that “Invalid SSL” persists
This should be fixed with new upgrade code that is pushed today.
Just upgraded it. Issue 1 is solved, https is intact after upgrade. A new issue aroused! Can’t login to panel! After providing username and password and clicking on login button brings to login page!
PLEASE FIX IT ASAP! IF ANYONE UPGRADES IT NOW IT MAY EFFECT THEM AS WELL!
Edit 1: You guys also added CloudLinux support? Dayum! Found a tab in “Server” section. Now you need a medium to large team for sure!
Edit: Didn’t knew I upgraded to build 1.8 version 6! :lol:
@CyberPanel had to reset “admin” pass to regain control of my panel. Please in future updates, fix this issue or that update will cripple “admin” pass and have to reset the pass again!
Steps I did,
Open a terminal/ SSH and type/ copy this → [python /usr/local/CyberCP/plogical/adminPass.py --password PASSWORD] EXACTLY YOU HAVE TO TYPE/ COPY THIS! LITERALLY! DO NOT TYPE/ COPY THE BRACKETS!@CyberPanel found a new issue! 
Backup doesn’t works! It say’s [cat: /home/example.com/backup/backupFileName: No such file or directory]
After upgrade your password should work, we just added session expire time nothing else. Anyways I will check.
Upgraded from version 1.8 build 4 to version 1.8 build 5. But there's some issues,
1. Still that "Invalid SSL" persists
2. "admin" user "First" and "Last" name has vanished!
3. "Server IP Address" also vanished!
4. Although I don't use "PowerDNS" but going to "panel/manageservices/managePowerDNS" shows "Error message: (1054, "Unknown column 'masterServer' in 'field list'")"
I will update this post if I find more issues ASAP!
I had the same problem when I updated the cyberpanel from 1.8.3 to 1.8.6.
I do not know what to do? Has anyone handled this error?
You are right about the user login issue and there was another minor issue I fixed and pushed the package. We recently released 1.8.6 and there are issues because of major changes. If you see anything do let us know.
For backup issue, since they now run as website user. You will have to just clear the backup directory or remove status file
rm -f /home/domain.com/backup/status
This should solve your backup issue.
@CyberPanel upgrading now, will let you know.
Edit: Ticket created! Check: Ticket #8I1B5R
@CyberPanel at the time of upgrading my net connection was unavailable Now if I run " python upgrade.py" it shows this,
[[root@server ~]# python upgrade.py
Traceback (most recent call last):
File “upgrade.py”, line 1598, in
main()
File “upgrade.py”, line 1594, in main
Upgrade.upgrade()
File “upgrade.py”, line 1517, in upgrade
Version = version.objects.get(pk=1)
File “/usr/lib64/python2.7/site-packages/django/db/models/manager.py”, line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File “/usr/lib64/python2.7/site-packages/django/db/models/query.py”, line 373, in get
num = len(clone)
File “/usr/lib64/python2.7/site-packages/django/db/models/query.py”, line 232, in len
self._fetch_all()
File “/usr/lib64/python2.7/site-packages/django/db/models/query.py”, line 1102, in _fetch_all
self._result_cache = list(self._iterable_class(self))
File “/usr/lib64/python2.7/site-packages/django/db/models/query.py”, line 53, in iter
results = compiler.execute_sql(chunked_fetch=self.chunked_fetch)
File “/usr/lib64/python2.7/site-packages/django/db/models/sql/compiler.py”, line 863, in execute_sql
sql, params = self.as_sql()
File “/usr/lib64/python2.7/site-packages/django/db/models/sql/compiler.py”, line 420, in as_sql
where, w_params = self.compile(self.where) if self.where is not None else ("", [])
File “/usr/lib64/python2.7/site-packages/django/db/models/sql/compiler.py”, line 373, in compile
sql, params = node.as_sql(self, self.connection)
File “/usr/lib64/python2.7/site-packages/django/db/models/sql/where.py”, line 79, in as_sql
sql, params = compiler.compile(child)
File “/usr/lib64/python2.7/site-packages/django/db/models/sql/compiler.py”, line 373, in compile
sql, params = node.as_sql(self, self.connection)
File “/usr/lib64/python2.7/site-packages/django/db/models/lookups.py”, line 169, in as_sql
lhs_sql, params = self.process_lhs(compiler, connection)
File “/usr/lib64/python2.7/site-packages/django/db/models/lookups.py”, line 162, in process_lhs
db_type = self.lhs.output_field.db_type(connection=connection)
File “/usr/lib64/python2.7/site-packages/django/db/models/fields/init.py”, line 640, in db_type
return connection.data_types[self.get_internal_type()] % data
File “/usr/lib64/python2.7/site-packages/django/utils/functional.py”, line 35, in get
res = instance.dict[self.name] = self.func(instance)
File “/usr/lib64/python2.7/site-packages/django/db/backends/mysql/base.py”, line 174, in data_types
if self.features.supports_microsecond_precision:
File “/usr/lib64/python2.7/site-packages/django/utils/functional.py”, line 35, in get
res = instance.dict[self.name] = self.func(instance)
File “/usr/lib64/python2.7/site-packages/django/db/backends/mysql/features.py”, line 53, in supports_microsecond_precision
return self.connection.mysql_version >= (5, 6, 4) and Database.version_info >= (1, 2, 5)
File “/usr/lib64/python2.7/site-packages/django/utils/functional.py”, line 35, in get
res = instance.dict[self.name] = self.func(instance)
File “/usr/lib64/python2.7/site-packages/django/db/backends/mysql/base.py”, line 385, in mysql_version
with self.temporary_connection() as cursor:
File “/usr/lib64/python2.7/contextlib.py”, line 17, in enter
return self.gen.next()
File “/usr/lib64/python2.7/site-packages/django/db/backends/base/base.py”, line 591, in temporary_connection
cursor = self.cursor()
File “/usr/lib64/python2.7/site-packages/django/db/backends/base/base.py”, line 254, in cursor
return self._cursor()
File “/usr/lib64/python2.7/site-packages/django/db/backends/base/base.py”, line 229, in _cursor
self.ensure_connection()
File “/usr/lib64/python2.7/site-packages/django/db/backends/base/base.py”, line 213, in ensure_connection
self.connect()
File “/usr/lib64/python2.7/site-packages/django/db/utils.py”, line 94, in exit
six.reraise(dj_exc_type, dj_exc_value, traceback)
File “/usr/lib64/python2.7/site-packages/django/db/backends/base/base.py”, line 213, in ensure_connection
self.connect()
File “/usr/lib64/python2.7/site-packages/django/db/backends/base/base.py”, line 189, in connect
self.connection = self.get_new_connection(conn_params)
File “/usr/lib64/python2.7/site-packages/django/db/backends/mysql/base.py”, line 274, in get_new_connection
conn = Database.connect(**conn_params)
File “/usr/lib64/python2.7/site-packages/MySQLdb/init.py”, line 81, in Connect
return Connection(*args, **kwargs)
File “/usr/lib64/python2.7/site-packages/MySQLdb/connections.py”, line 193, in init
super(Connection, self).init(*args, **kwargs2)
django.db.utils.OperationalError: (2003, 'Can\‘t connect to MySQL server on \‘127.0.0.1\’ (111 “Connection refused”)’)]
I will create a ticket ASAP!
So is the consensus to wait on upgrading to 1.8.6 now too? CyberPanel support just fixed all my 1.8.5 issues but I won’t upgrade if there are issues with this new release until they get sorted out.
@Hifihedgehog support team fixed my issue about upgrading! @CyberPanel THANKS A LOT! Also great news for all! Issue 1-4 all has been solved! Anyone can upgrade to build 1.8 version 6. But backup isn’t fixed yet.
For backups you need to remove your backup directory so new structure can be created
rm -rf /home/domain.com/backup/*
Let me know if still won’t after. Because I can’t reproduce on my end.
@CyberPanel said:
@minhazulOO7For backups you need to remove your backup directory so new structure can be created
rm -rf /home/domain.com/backup/*
Let me know if still won’t after. Because I can’t reproduce on my end.
I have removed the “status” file as you mentioned before. But didn’t worked. Now let’s see what happens if I remove “backup” directory 
@minhazulOO7 said:
@Hifihedgehog support team fixed my issue about upgrading! @CyberPanel THANKS A LOT!Also great news for all! Issue 1-4 all has been solved! Anyone can upgrade to build 1.8 version 6. But backup isn’t fixed yet.
I just upgraded and now email accounts are broke. I and the rest of my users cannot access any of our email accounts. I just created a ticket. Please fix this ASAP!
@CyberPanel deleted “backup” folder and tried backup but again same result. Let me explain what happens,
@pauloandres said:
Hi, I have another issue added to those of minhazulOO7.
After upgrade all the emails password don’t work. To correct it, I had to change the passwords of each email
@Hifihedgehog bro check this, @pauloandres bro posted this after upgrading to build 1.8 version 5. I don’t use CyberPanel email that’s why don’t know of this issue.
Im not sure if its due to the upgrade or what, but I have onyl use 1.8.5 and above and backups have not worked on both premade Digital Ocean servers or self-installed. Emails aren’t working either it appears.
“Running cat: /home/my.domain.com/backup/backupFileName: No such file or directory”
When running backups
@minhazulOO7 said:
@pauloandres said:
Hi, I have another issue added to those of minhazulOO7.
After upgrade all the emails password don’t work. To correct it, I had to change the passwords of each email@Hifihedgehog bro check this, @pauloandres bro posted this after upgrading to build 1.8 version 5. I don’t use CyberPanel email that’s why don’t know of this issue.
Just to clarify, I had asked about 1.8.6 and I upgraded to 1.8.6 and that is when the problems started with emails. I had no email authentication or log in issues until 1.8.6. 1.8.5 had no issues at all with email.
@CyberPanel more issues! I have disabled “PowerDNS” because I don’t need it. Is this the cause why backup’s not working? Also when I tried to enable “PowerDNS” by selecting “Default” function mode it shows “Changes successfully applied” but reloading the “PowerDNS” service page shows it’s disabled! Also checked “serverstatus/services” “PowerDNS” is running! Because “PowerDNS” service page shows it’s disabled, in the sidebar menu no “DNS” option is available.
@Hifihedgehog said:
@minhazulOO7 said:
@pauloandres said:
Hi, I have another issue added to those of minhazulOO7.
After upgrade all the emails password don’t work. To correct it, I had to change the passwords of each email@Hifihedgehog bro check this, @pauloandres bro posted this after upgrading to build 1.8 version 5. I don’t use CyberPanel email that’s why don’t know of this issue.
Just to clarify, I had asked about 1.8.6 and I upgraded to 1.8.6 and that is when the problems started with emails. I had no email authentication or log in issues until 1.8.6. 1.8.5 had no issues at all with email.
Although changing email pass isn’t a feasible option, let’s wait it will be fixed.
Which password scheme did you use before v1.8.6 ?
Passwords were unencrypted as they came with CyberPanel.
looks like MD5 or something.
That’s the bug I describe in the ticket, CyberPanel. They became MD5 encrypted only after I ran the update for 1.8.6. They were originally unencrypted prior to running the update.
They should be in the {CRYPT} format after upgrade.
If you have plain passwords from your backups, kindly restore them and re-upgrade make sure they are in crypt format.
They should be but the upgrade converted them to MD5. Can you please fix this since this was a bug in your code? Thanks!
We converted them to CRYPT format. Anyways you can open /etc/dovecot/dovecot.conf
and paste auth_mechanisms = cram-md5 and then do systemctl restart dovecot
See if your issue is resolved.
No, that didn’t work. To confirm, I did the following:
To repeat, my recent upgrade timeline was this.
I noticed what you did. You converted all the email passwords now to CRAM-MD5. As I stated from the beginning, when the passwords are in MD5, logins fail. If I create new emails accounts, the new email account system in 1.8.6 encrypts those new emails’ passwords with CRYPT. I am not sure if you are aware of this, but CRYPT is what the new system is using for email logins and for creating new email accounts. As a result, CRYPT works. MD5 doesn’t. The way to fix this, I believe is.
For those who are upgrading, your script, as it stands, encrypts those with preexisting, unencrypted email accounts to MD5 and that simply does not work.
Note that I restored my e_users table files to the following location:
/root/temp/lib/mysql/cyberpanel
There are the frm and ibd files for e_users. Note that you cannot simply copy them over since you changed the table definition and it will not be accepted by the MariaDB SQL dictionary. But that passwords are there so hopefully you can manage to restore them since I personally don’t have the tools to efficiently extract them. Thanks!
what is output of cat /etc/dovecot/dovecot-sql.conf.ext
Make sure to mask your passwords.
Here is the output:
driver = mysql
connect = host=localhost dbname=cyberpanel user=cyberpanel password=* port=3306
password_query = SELECT email as user, password FROM e_users WHERE email=’%u’;
I readded the line, restarted dovecot and even rebooted my server. Email logins fail despite all that.
Ah, found it! Traversing to the subfolder /etc/dovecot/conf.d/, there is a 10-auth.conf file. There, the line auth_mechanisms = is found, but it is defined as “plain” only. This file supersedes and takes precedence over whatever is specified in the dovecot.conf file in the parent folder. Your upgrade script should have edited this line to include MD5 because the script as it was inadvertently converted all the email passwords to irreversible MD5 hashes.
To sum it up, the fix is simple:
After that, everything should work as before. I hope this helps anyone else experiencing the same difficulties as I did!
I have an issue with your use of CRYPT with new accounts and MD5 for migrating old ones. Either all the accounts need to be MD5 or they all need to be CRYPT for SQL scripting I use to work properly. I have a password changing system in my email system and I also have a PHP email registration page as well that need consistency in encryption to work. Neither can work consistently unless the system uses MD5 throughout since all my old accounts, due to the mistake in the migration code from 1.8.5 to 1.8.6, are all MD5 hashed. Can you change your code to encrypt with MD5 for new accounts? Otherwise, I have to tell all my users they will be losing their passwords and I will get the heat from them, let me tell you.
Help! I just updated to 1.8.7 since it said was an urgent update when, in reality, it introduced email issues for me again. Now, after fixing the MD5 problem, none of my users’ emails are accessible again. There is also a new issue. I cannot make new email accounts even with CyberPanel. The system error is: Cannot create email account. Error message: ‘passwordByPass’
Edit 3: Also forgot to add! Disabling “PowerDNS” disabled it perfectly! But re-enabling it doesn’t show it’s “enable” on “manageservices/managePowerDNS”. If I go to “serverstatus/services” it shows “PowerDNS” is enabled after I re-enabled it. That mean’s there’s something fishy going on with “manageservices/managePowerDNS” page.
Edit 2: Checked again, backups are really working! Just those errors are there and backup size isn’t correct (Edit 1).
Edit 1: Strange 
Backup is really working but showing errors,
[Running cat: /home/example.com/backup/backupFileName: No such file or directory Completed]
[42 backup-example-10-52-59-Tue-Jul-2019 10-52-59-Tue-Jul-2019 0 Completed]
These ^ errors shown after I have successfully backed up a site. Yes, I have deleted “backup” folder before. Also going to the “backup” folder I am getting a full fledged CyberPanel backup tar.gz file!
Edit: Nope! Again backups acting weird again! 
@CyberPanel H O L Y! After upgrading to build 1.8 version 7 backup’s working again! 
For passwordByPass issue, just clear your browser cache.
But we can not change password scheme for dovecot.
I will try to reproduce the issue number 3.
After upgrading I wasn’t able to log into my email accounts. I changed passwords and everything seems fine, I can send emails but I cant receive, the server does not reply any error message, I just don’t get any new messages on my inbox.
Please help!
I can´t login with the emails in rainloop the email is not working is a fresh installation CP 1.8.7 .
