Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

[theunknownstuntman]

Server operating system version

20.04.6 LTS (Focal Fossa)

Plesk version and microupdate number

Version 18.0.67 Update #2

Hi all,

since today I receive the following error message, when I run, for example, the command "apt list exim". As I did not modify anything on the server
in the last days and no changes where applied as part of "unattended-upgrades", I am a bit clueless, where this error comes from and how to fix it, as I don't want to mess with keys related to plesk repositories.

Unfortunately this link is no help.

https://support.plesk.com/hc/en-us/articles/14324248261911-Can-t-open-Plesk-updates-Conflicting-values-set-for-option-Signed-By-regarding-source

I use Plesk Obsidian Web Host Edition.

I appreciate any help. Thanks.

E: Conflicting values set for option Signed-By regarding source Index of /PMM_1.0.0 focal: /etc/apt/keyrings/plesk-ext-panel-migrator.gpg != /etc/apt/keyrings/plesk-ext-site-import.gpg
E: The list of sources could not be read.
E: Conflicting values set for option Signed-By regarding source Index of /PMM_1.0.0 focal: /etc/apt/keyrings/plesk-ext-panel-migrator.gpg != /etc/apt/keyrings/plesk-ext-site-import.gpg
E: The list of sources could not be read.

 

[theunknownstuntman]

I thought I could fix the issue by updating Plesk to Version 18.0.67 Update #3. Unfortunately I can not open https://plesk.server.domain:8447, when I open Tools & Settings, "Updates" in Plesk

 

[scsa20]

Look for any additional sources in /etc/apt/sources.list.d, chances are have a duplicate source there.

Also if you want to try to upgrade your plesk installation you can run of the following command depending on if you want to upgrade everything or just the panel.

Everything:

plesk installer --select-release-latest --upgrade-installed-components

Just Plesk:

plesk installer install-panel-updates

 

[theunknownstuntman]

Thank you for your help. I can not identify any duplicates on /etc/apt/sources.list.d

focal-icinga.list
imunify360.list
imunify-rollout-bypass.list.disabled
imunify-rollout.list
imunify-rollout.list.save
kcare.list
kcare.list.save
plesk-ext-docker.list
plesk-ext-docker.list.save
plesk-ext-grafana.list
plesk-ext-grafana.list.save
plesk-ext-panel-migrator.list
plesk-ext-site-import.list
plesk.list
plesk.list.save

Isn't the problem to search here in /etc/apt/keyrings/ ?

 

[theunknownstuntman]

plesk installer install-panel-updates

This command does not work, because of the mentioned error.

Synchronizing the Debian APT package index files...
E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/ focal: /etc/apt/keyrings/plesk-ext-panel-migrator.gpg != /etc/apt/keyrings/plesk-ext-site-import.gpg
E: The list of sources could not be read.
Warning: there are errors in 'apt-get update'
E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/ focal: /etc/apt/keyrings/plesk-ext-panel-migrator.gpg != /etc/apt/keyrings/plesk-ext-site-import.gpg
E: The list of sources could not be read.
E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/ focal: /etc/apt/keyrings/plesk-ext-panel-migrator.gpg != /etc/apt/keyrings/plesk-ext-site-import.gpg
E: The list of sources could not be read.

Funny is, that the files /etc/apt/keyrings/plesk-ext-panel-migrator.gpg and /etc/apt/keyrings/plesk-ext-site-import.gpg are identical. So the error above does not make sense at all...

 

[theunknownstuntman]

Moving mv plesk-ext-site-import.list out of the the /etc/apt/sources.list.d/ directory, fixed the issue.

I wonder how this can happen. In my opinion this is a bug in Plesk.

 

[Sebahat.hadzhi]

The error typically indicates that there is an issue with the repository configuration in the system. I personally wouldn't say this is a Plesk bug. The repository itself is not necessarily misconfigured, it is the system’s handling of the repository that’s causing the conflict. Still, I might be mistaken and if you wish for the case to be further investigated, please open a support case. At this point, I don't have enough evidence to report that as a bug.

 

[theunknownstuntman]

The error typically indicates that there is an issue with the repository configuration in the system. I personally wouldn't say this is a Plesk bug. The repository itself is not necessarily misconfigured, it is the system’s handling of the repository that’s causing the conflict. Still, I might be mistaken and if you wish for the case to be further investigated, please open a support case. At this point, I don't have enough evidence to report that as a bug.

Thank you for your answer. Could you mark the topic as resolved? Might help others, having the same problems.