Resolved Cannot update

[Kniar]

Server operating system version

CentOS 7.9

Plesk version and microupdate number

18.0.75

Hello,

I have 2 old CentOS 7 with Plesk Obsidian 18.0.75 ELS. I cannot install any updates, either using yum or using the Plesk interface, because of the Tuxcare repo. How to fix it as we pay ELS in order to have updates still working ? Thanks to not answer me something like "you should consider upgrading your OS".

# yum update
Loaded plugins: fastestmirror
Determining fastest mirrors
epel/x86_64/metalink | 3.6 kB 00:00:00
* epel: d2lzkl7pfhq30w.cloudfront.net
PLESK_17_PHP54 | 2.9 kB 00:00:00
PLESK_17_PHP55 | 2.9 kB 00:00:00
PLESK_17_PHP56 | 2.9 kB 00:00:00
PLESK_17_PHP70 | 2.9 kB 00:00:00
PLESK_17_PHP71 | 2.9 kB 00:00:00
PLESK_17_PHP72 | 2.9 kB 00:00:00
PLESK_17_PHP73 | 2.9 kB 00:00:00
PLESK_17_PHP74 | 2.9 kB 00:00:00
PLESK_17_PHP81 | 2.9 kB 00:00:00
PLESK_17_PHP83 | 2.9 kB 00:00:00
PLESK_18_0_75-extras | 2.9 kB 00:00:00
alt-common | 3.0 kB 00:00:00
base | 3.6 kB 00:00:00
https://repo.tuxcare.com/centos7-el...JhwsnmwTfx/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
Trying other mirror.
To address this issue please refer to the below wiki article

yum-errors - CentOS Wiki

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



One of the configured repositories failed (CentOS 7 Extended Lifecycle Support by TuxCare),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=centos7-els ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable centos7-els
or
subscription-manager repos --disable=centos7-els

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=centos7-els.skip_if_unavailable=true

failure: repodata/repomd.xml from centos7-els: [Errno 256] No more mirrors to try.
https://repo.tuxcare.com/centos7-el...JhwsnmwTfx/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden

 

[scsa20]

This is not a Plesk error, this is an error with TuxCare and the error you're getting is a forbidden. From the looks each system has their specific repo for the extended supported OS. Your specific repo is being blocked (either the key used for accessing expired or something).

My suggestion is to make sure your license key is still valid and try re-running the setup for the repo (assuming your license for TuxCare is still good, this can be checked at https://portal.tuxcare.com/ (or from Platform360 if you bought through Plesk or check your VPS provider).

Otherwise your best bet is to contact TuxCare support.

Thanks to not answer me something like "you should consider upgrading your OS".

You really should consider upgrading though, but considering TuxCare is going to provide support for CentOS 7 until 2029 you have time to plan out the move.

 

[Kniar]

I've never subscribed to tuxcare. I even don't know what is it. It should have been added by Plesk (in ELS contaxt I suppose). My 2 servers are affected.

 

[scsa20]

Then you would need to subscribe to TuxCare. Your VPS provider might also have an agreement for a low price so you'll need to double check with them. And pretty sure you can buy a license through Plesk as well through the TuxCare extension (but all the extension does is configures the tuxcare repo).

Either case, without being subscribed you won't be able to utilize the tuxcare els repos.

 

[Kniar]

I pay standard Plesk Lisense + I pay Plesk ELS... and I have to pay Tuxcare ELS also ? So what is Plesk ELS addon for ?

 

[scsa20]

Plesk ELS uses TuxCare. As I've mention, if you have a license already, make sure it's still valid (in this case you can confirm by looking into platform360), reapply the license as well if you need to.

 

[Sebahat.hadzhi]

@Kniar , if reapplying the license doesn't solve the issue. Please provide me with your server IP address in a private message so I can get our team to check if there's an issue with the license.

 

[Kniar]

@Sebahat.hadzhi I reapplied the lisense and it works ! I can yum update again. Thanks for tip !

 

[scsa20]

Good to hear that reapplying the license worked o7