Issue Auto update problem

[Symer]

Hello all,
First of all I apologize for my English.
I am a brand new user of Plesk Obsidian (v.18.0.34). I just took out my subscription.

However, I have an error message regarding an update :

Raison : 2021-03-11 00:33:18 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2021-03-11 00:33:21 ERROR: W:GPG error: Index of /kernelcare-debian/6/ stable InRelease: The following signatures were invalid: E58FE9B3FE3B0470525159BD6DC3D600CDEF74BB, E:The repository 'Index of /kernelcare-debian/6/ stable InRelease' is not signed.
2021-03-11 00:33:21 ERROR: Exited with returncode 1.

Can you help me please ?
I don't really understand why my signature is invalid and how to change it ?

-----------------------------
And a quick question for the road.
On my subscription for the moment I have the right to 10 domains. Does an Alias count as a domain ?

Thank you in advance for your answers

 

[IgorG]

I think this problem is addressed in the following KB article: Plesk update fails: GPG error: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY

 

[Symer]

Thanks for your quick return. It is quite possible that it is that yes!

So i tried

sudo apt-key adv --keyserver Index of /kernelcare-debian/6/ --recv-keys

But first problem, I don't have sudo install on my server. (sudo: command not found)

 

[IgorG]

I don't have sudo install on my server. (sudo: command not found)

Install it with:

apt-get install sudo

 

[Symer]

Great, thank you ! I applied that and now he's telling me.

Error: The System Updates tool is already installing updates in automatic mode. Try later.

So more than to wait to see if everything is good

 

[Symer]

However, I see this line on SSH :

Executing: /tmp/apt-key-gpghome.na4ryM0Tsk/gpg.1.sh --keyserver Index of /kernelcare-debian/6/ --recv-keys E58FE9B3FE3B0470525159BD6DC3D600CDEF74BB
gpg: keyserver receive failed: No data

Not sure it worked ...

 

[Symer]

Hello, The test is not successful. I still have the same problem.
Do you have another idea please?

 

[IgorG]

Have you applied a solution from the mentioned KB article?

 

[Symer]

I think yes. But this not work

 

[IgorG]

I think yes. But this not work

Contact Plesk Support Team in this case.

 

[Symer]

Ok thx