hi after update cyberpanel. I do not access my cyberpanel dashboard . typing https://my server IP address:8090/ not open cyberpanel dashboard open phpmyadmin please help me
Not really fix but try go around above
working working working i love you
Run this command exactly how you ran the one to install cyberpanel:
sh <(curl https://raw.githubusercontent.com/tbaldur/cyberpanel-fix-23-06-2022/main/fix.sh || wget -O - https://raw.githubusercontent.com/tbaldur/cyberpanel-fix-23-06-2022/main/fix.sh)
you create the fix ?
Please tell me what command needs to use if I am using Potty Login as a root.
login SSH as root > root with password > than type this command " sh <(curl https://raw.githubusercontent.com/usmannasir/cyberpanel/stable/preUpgrade.sh || wget -O - https://raw.githubusercontent.com/usmannasir/cyberpanel/stable/preUpgrade.sh)"
Is that correct? or any more steps to follow.
Very first take server snapshot if something go wrong.
I have upgraded ubuntu to 22.04 (silly mistake!). Cyberpanel gives 503 error. When I run upgrade command it says:
"Unable to detect your system…
CyberPanel is supported on x86_64 based Ubuntu 18.04, Ubuntu 20.04, Ubuntu 20.10, Ubuntu 22.04, CentOS 7, CentOS 8, AlmaLinux 8, RockyLinux 8, CloudLinux 7, CloudLinux 8, openEuler 20.03, openEuler 22.03…"
Funny thing is Ubuntu 22.04 is in the list of supported OS!
Tried to upgrade today to latest and it got stuck on this:
Should I just force close it or what should I do?
not my first time to update cyberpanel and I check updates regularly. First time update script got stuck.
error:
sed: can’t read /usr/local/lsws/conf/httpd.conf: No such file or directory
sed: -e expression #1, char 89: unterminated `s’ command
sed: -e expression #1, char 89: unterminated `s’ command
Version management says it is now latest version:
ctrl + c did the trick, and upgrade continued to the end
[09.05.2022_21-02-41] #########################################################################
[09.05.2022_21-02-41] /root/.acme.sh/acme.sh --upgrade --auto-upgrade successful.
[09.05.2022_21-02-41] #########################################################################
[Mon 05 Sep 2022 09:02:41 PM UTC] Changed default CA to: https://acme-v02.api.letsencrypt.org/directory
[09.05.2022_21-02-41] #########################################################################
[09.05.2022_21-02-41] /root/.acme.sh/acme.sh --set-default-ca --server letsencrypt successful.
[09.05.2022_21-02-41] #########################################################################
sed: can’t read /usr/local/lsws/conf/httpd.conf: No such file or directory
sed: -e expression #1, char 89: unterminated s' command sed: -e expression #1, char 89: unterminated
s’ command
sed: -e expression #1, char 89: unterminated s' command sed: -e expression #1, char 89: unterminated
s’ command
sed: -e expression #1, char 89: unterminated s' command sed: -e expression #1, char 89: unterminated
s’ command
sed: -e expression #1, char 89: unterminated s' command sed: -e expression #1, char 89: unterminated
s’ command
sed: -e expression #1, char 89: unterminated s' command sed: -e expression #1, char 89: unterminated
s’ command
sed: -e expression #1, char 89: unterminated s' command sed: -e expression #1, char 89: unterminated
s’ command
sed: -e expression #1, char 89: unterminated s' command sed: -e expression #1, char 89: unterminated
s’ command
sed: -e expression #1, char 89: unterminated s' command sed: -e expression #1, char 89: unterminated
s’ command
sed: -e expression #1, char 89: unterminated s' command sed: -e expression #1, char 89: unterminated
s’ command
sed: -e expression #1, char 89: unterminated s' command sed: -e expression #1, char 89: unterminated
s’ command
sed: -e expression #1, char 89: unterminated `s’ command
I have got the same issue. What did solve it?
Ctrl + C and then my upgrade continued to the end. I thin Ctrl + C closes that task, but script continues.
Great, that worked. Thanks
Ok work but not a good or real resolution
no it is not. But that way you can finish upgrade until devs fix upgrade script.
I have same issue @usmannasir @shoaibkk any fix for this or just skipping is solution?
For below error use command rm /etc/sysconfig/imunify360/integration.conf
and run update again.
09.15.2022_07-44-49] #########################################################################
[09.15.2022_07-44-49] /root/.acme.sh/acme.sh --upgrade --auto-upgrade successful.
[09.15.2022_07-44-49] #########################################################################
[Thu 15 Sep 2022 07:44:49 AM UTC] Changed default CA to: https://acme-v02.api.letsencrypt.org/directory
[09.15.2022_07-44-49] #########################################################################
[09.15.2022_07-44-49] /root/.acme.sh/acme.sh --set-default-ca --server letsencrypt successful.
[09.15.2022_07-44-49] #########################################################################
[09.15.2022_07-44-49] #########################################################################
[09.15.2022_07-44-49] sed -i ‘/CyberCP/d’ /etc/crontab successful.
[09.15.2022_07-44-49] #########################################################################
sed: -e expression #1, char 89: unterminated
s' command sed: -e expression #1, char 89: unterminated
s’ command
sed: -e expression #1, char 89: unterminateds' command sed: -e expression #1, char 89: unterminated
s’ command
sed: -e expression #1, char 89: unterminateds' command sed: -e expression #1, char 89: unterminated
s’ command[09.15.2022_07-44-49] #########################################################################
[09.15.2022_07-44-49] find /usr/local/lsws/conf/vhosts/ -type f -name ‘vhost.conf’ -exec sed -i “s/.CustomLog./ LogFormat ‘%h %l %u %t “%r” %>s %b “%{Referer}i” “%{User-Agent}i”’ combined
&/g” {} ; successful.[09.15.2022_07-44-49] #########################################################################
@nick.chomey … as it would turn out, it was /usr/bin/pip* soft links, linking to CloudLinux pip & python files. reinstalling a few python packages was certainly a lot easier than spinning up a new VPS!
it looks as though I was finally able to update CyberPanel, although I still have a few things that need fixing.
After upgrading cyberpanel today, stuck here with lscpd unable to start.
Starting LSCPD Daemon…
./lscpd: /lib64/libc.so.6: version `GLIBC_2.25’ not found (required by ./lscpd)
[ERROR] Failed to start lscpd!
This is on CentOS 7.9-2009.
So I tried rolling back to CP 2.3.1 and now hostname:8090 goes to phpmyadmin login instead of CP login page. Have no idea what’s going on…