• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Plesk Control Panel unreachable after update to Onyx

Jeroen Bl

New Pleskian
After I updated my Plesk 12 installation to Onyx I ran into some issues regarding missing dependencies for libopendkim. I was able to work around this issue by following the following KB thread:

https://support.plesk.com/hc/en-us/...4-17-x86-64-requires-libopendkim-so-10-64bit-

This indeed worked in that the updater was able to finish. Installing # yum install opendkim.x86_64 after enabling epel and atomic repositories gave some issues, but as far as I can see finished installing.

However, after the update to Onyx my control panel is not accessible.
Websites runs as normal, mail clients as well.

It is just the controlepanel that returns with a ERR_CONNECTION_REFUSED.

What i've done:

- restarted Plesk (not server)
- checked for enough space in, for example, /tmp
- checked error logs:
- disabled SSO by -> /usr/local/psa/bin/sso --disable (I read somewhere this worked, alas)
  • Error log: /var/log/sw-cp-server/error_log and /var/log/sw-cp-server/sw-engine.log
  • Access log: /usr/local/psa/admin/logs/httpsd_access_log
  • Panel log: /usr/local/psa/admin/logs/panel.log
Which didn't tell me anything

I would love someone to help me. Thanks!
 
1. Check that you have the same ssl port here:

# grep ssl /etc/sw-cp-server/conf.d/plesk.conf
listen 8443 ssl;
ssl_certificate /opt/psa/admin/conf/httpsd.pem;
ssl_certificate_key /opt/psa/admin/conf/httpsd.pem;

2. Try to repair installation with

# plesk repair installation

3. Apply all available microupdates with

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

4. Try to reboot server.
 
Hi Igor,

Thanks for your quick reply! I have followed your "Steps":

1) This was correct, listen 8443 SSL
2) Plesk repair installation fails with message:

trying to start service sw-cp-server…sw-cp-serverd is stopped
starting sw-cp-server failed
Warning!
some problems are found during the start service sw-cp-server(see log file: /var/log/plesk/rc_actions.log)

The log says the same.

3) After installing microupdates my server responded with:

Starting sw_cp_server service ... failed
Starting mysql service... failed
Starting tomcat service... not installed

ERROR: An error occurred during performing of installation POST actions (see log for details)
Warning! Not all packages were installed.
Please check if your system services are operable.
Please resolve this issue and try to install the packages again.
If you cannot resolve the issue on your own, contact product technical support for assistance.
Exit status 1
As this made my websites inoperable I placed my backup back. So I am not able anymore to see logs or check the installation.

I am hoping that this information can give you an idea of what could be wrong. It's a shame, I was really looking forward to the Onyx update.

 
Back
Top