• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Plesk update fails on CentOS 7 + TuxCare ELS: missing trousers dependency (gnutls requires trousers >= 0.3.11.2)

AlbertoPizzarelli

New Pleskian
Server operating system version
Centos 7.9 With TuxCare EOL on board
Plesk version and microupdate number
18.0.76
Hi everyone,
I wanted to share a solution that helped me resolve a dependency issue during the latest Plesk (18.0.79) update on a CentOS 7 server protected by TuxCare Extended Lifecycle Support (ELS).

Environment​

  • CentOS 7
  • Plesk Obsidian
  • TuxCare ELS enabled

Error​

During the Plesk update, the installer stopped with the following dependency error:

Failed to solve dependencies:

gnutls-3.3.29-9.el7_9.tuxcare.els5.x86_64
requires trousers >= 0.3.11.2

The package trousers was not available in the configured repositories, preventing the update from completing.

Solution​

I manually installed the required RPM from the CentOS Vault mirror:

wget ftp://ftp.icm.edu.pl/vol/rzm5/linux-centos-vault/7.0.1406/os/x86_64/Packages/trousers-0.3.11.2-3.el7.x86_64.rpm

Then installed it with:

rpm -i trousers-0.3.11.2-3.el7.x86_64.rpm

After installing the package, I ran the Plesk update again, and it completed successfully without any further issues.

Notes​

  • This happened on a server where TuxCare ELS was already correctly installed and active.
  • The missing dependency appears to be the only blocker.
  • Installing the trousers package manually resolved the issue immediately.
Hopefully this saves someone else some troubleshooting time.
If the Plesk team considers it appropriate, it might be worth checking whether this dependency could be handled automatically during updates on CentOS 7 + TuxCare ELS systems.
I hope this helps!
 
Molto interessante. Very interesting.
I've the same issue on my CentOS 7 and my panel can't update since the 18.0.76.
Now the question is... how risky is this workaround considering that i'm running 80 websites on that phisical server?
 
Hi D4NY,

I completely understand your concern, especially on a production server hosting 80 websites.

I can only speak from my own experience: on my CentOS 7 server with TuxCare ELS enabled, installing the missing trousers-0.3.11.2-3.el7.x86_64 package resolved the dependency issue and allowed the Plesk update to complete successfully. I haven't experienced any related problems since then.

That said, I wouldn't describe the workaround as completely risk-free for every environment. It involves manually installing a package from the CentOS 7 Vault in order to satisfy a dependency required by the TuxCare ELS version of gnutls.

On a production server with 80 websites, I would definitely recommend having a full and verified backup before proceeding and, if possible, testing the RPM installation first or checking the transaction/dependencies before actually installing it.

In my case, trousers was simply the missing dependency and no existing packages needed to be removed or downgraded.

It would also be useful if someone from Plesk or TuxCare could confirm whether this is still the recommended approach, since apparently I'm not the only one affected by this issue.

If you decide to try it, I would suggest checking the RPM and dependencies first rather than installing it immediately.

Hope this helps!
 
Grazie mille per la risposta.
Your workaround sounds easy to follow, installing the package should not impact Plesk directly.
But at the same time now my Plesk is working perfectly even if it hasn't the last updates.
Mine is not a VPS (but a dedicated server) so i can't take a snapshot to restore immediatly in case of disaster.
I think at the moment i'll go on with current version. Thanks a lot again
 
Back
Top