Resolved Unable to get key: Repository is not opened

[Pascal_Netenvie]

Perhaps this could be auto fixed by Plesk repair tool or during Plesk upgrade process ...

 

[Jürgen_T]

So, now it was investigated by Level 1 and 2 support of the Plesk Team. It is a bug. Here comes the final answer:

....
Hello ,

Thank you for waiting

Our developer's team confirmed such behavior to be a bug with ID: PPPM-13853

Currently there is no workaround provided. You may observe changes in our Plesk change log

Thank you for bringing it to our attention.

Should you have additional questions let me know.
Best regards,
Aleksei Khikhich
Technical Support Engineer
Plesk

...

So we have to wait until the Plesk developers will fix it in one of the upcoming updates.

 

[Pascal_Netenvie]

Hello Kulturmensch,
Thanks for the news !

 

[mow]

Does this happen when registry.xml grows too big? It was 65768 bytes here (just over 64KB), and after removing and retrieving it has just 950 bytes.

 

[Jürgen_T]

The bug ID: PPPM-13853 with the result: "Unable to get key: Repository is not opened" is still open since the update Plesk Obsidian 18.0.52.3 this night.

 

[Peter Debik]

It is only a cosmetic "error", so it does not get the highest priority in fixing efforts. You can ignore the error. It also consumes a few Bytes of log length only, nothing to worry about.

 

[Jürgen_T]

The bug ID: PPPM-13853 with the result: "Unable to get key: Repository is not opened" is still open since the update Plesk Obsidian 18.0.53 this night.

 

[Jürgen_T]

Unable to get key: Repository is not opened
Still there since the update 18.0.53 /2 tonight

 

[Polli]

root@mail:/# mv /etc/sw/keys/registry.xml /root/
root@mail:/# service sw-engine restart
root@mail:/# plesk repair fs -system -y

Checking Linux system files ......................................... [OK]
Error messages: 0; Warnings: 0; Errors resolved: 0

root@mail:/# /usr/local/psa/bin/license --retrieve
Updating Plesk license key: Done
root@mail:/#

They recommended to test the result with the command:
root@mail:/#plesk daily

After doing all these steps. There is an error message in the logs.

Result of interface implementation call: failure: SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed: Licenses.id, query was: INSERT INTO "Licenses" ("id", "description", "vendor", "nextUpdate") VALUES (?, ?, ?, ?)

Can I ignore this? Or is it fixable by myself?

best regards

 

[Peter Debik]

@Polli The issue is a known bug with ID #EXTPLESK-4926 for the Support SSH Access extension and will be fixed in a future version of the extension. You may look for status updates in relation to this bug in the Plesk Change Log.
The error message itself has no actual impact on the extension or Plesk itself and can be safely ignored.

 

[woocommerce-premium]

The problem still persists for me:

2024-04-21 00:00:10

ERR

panel [1239739:66243aea0ac8b]

Unable to get key: Repository is not opened

 

[JuanCar]

The issue has not been fixed in las update (18.0.2 Update 2)

2024-08-06 00:00:03

ERR

panel [637642:66b14b6374918]

Unable to get key: Repository is not opened

 

[crnunez]

Hi, the issue is persistent. When will you solve this?

 

[Sebahat.hadzhi]

There's no ETA for the release of this bug fix yet. It has relatively low priority considering it is just "cosmetic" and has no actual negative impact. We appreciate everyone's patience and understanding on the matter.

A possible workaround we can suggest at the time being is to try uninstalling and re-installing the "Support SSH Access" extension. I hope that helps.

 

[AYamshanov]

The issue is a known bug with ID #EXTPLESK-4926 for the Support SSH Access extension and will be fixed in a future version of the extension.

A new version of the extension has been released,

1.2.6 (29 Nov 2024)​

• The default SSH access period is extended to 14 days to prevent expiration during support ticket investigations.
• [-] Updates to license keys no longer cause tasks with "Integrity constraint violation" error to appear in task manager. (EXTPLESK-4926)

---

[...] Unable to get key: Repository is not opened [...]

It is another bug; it has not been fixed yet.

 

[AYamshanov]

Hi! The latest release contains the fix for the issue with "Unable to get key: Repository is not opened",

Plesk Obsidian 18.0.68 4, March 2025
[...]
- The /var/log/plesk/panel.log file no longer contains the “Unable to get key: Repository is not opened” errors that were generated daily under specific circumstances. (PPP-59722)