• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Unable to get key: Repository is not opened

Kulturmensch

Kulturmensch

Regular Pleskian
Server operating system version
Ubuntu 20.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian v18.0.48_build1800221104.03
One time a day the following error messages appear in my panel protocoll

[2022-12-16 06:35:57.990] 240999:639c03bdf1508 ERR [panel] Unable to get key: Repository is not opened
[2022-12-16 06:35:58.023] 240999:639c03bdf1508 ERR [panel] Unable to get key: Repository is not opened
[2022-12-16 06:35:58.023] 240999:639c03bdf1508 ERR [panel] Unable to get key: Repository is not opened
[2022-12-16 06:35:58.054] 240999:639c03bdf1508 ERR [panel] Unable to get key: Repository is not opened

Any idea, how to get more information/how to solve it?
 
In addition apt update does not show any errors?

~# apt update
OK:1 http://ftp.stratoserver.net/pub/linux/ubuntu focal InRelease
OK:2 http://ftp.stratoserver.net/pub/linux/ubuntu focal-updates InRelease
OK:3 http://ftp.stratoserver.net/pub/linux/ubuntu focal-security InRelease
OK:4 http://ftp.stratoserver.net/pub/plesk/pool/PSA_18.0.48_10183 focal InRelease
OK:5 http://ftp.stratoserver.net/pub/plesk/PHP74_17 focal InRelease
OK:6 http://ftp.stratoserver.net/pub/plesk/PHP80_17 focal InRelease
OK:7 http://ftp.stratoserver.net/pub/plesk/PHP81_17 focal InRelease
OK:8 Index of /grafana/deb stable InRelease
OK:9 Index of /mariadb/repo/10.6/ubuntu/ focal InRelease
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Alle Pakete sind aktuell.
 
Thank you for the help. This is the result:

plesk repair fs -system -y

Checking Linux system files ......................................... [OK]

Error messages: 0; Warnings: 0; Errors resolved: 0

Could it be, that the Plesk bug with ID #PPPM-9001 fixed in Plesk Onyx 17.8 for Windows on April 17th, 2018. Fix for Plesk for Linux is expected in future updates did come back?
 
Just checked whether the plesk license key can be received via command line. Result:
# plesk bin license --retrieve
Updating Plesk license key: Done

So it seems not to be the old bug #PPPM-9001

However, I have no idea from where the panel errors come from.
 
I saw this artcle but as the content of /etc/sw/keys/info is sw-key-repository-1.0 what seems to be correct I did not proceed further.
 
The error came up today:
2022-12-18 11:05:11ERRpanel [580152:639ee5d7ca4d5]Unable to get key: Repository is not opened
2022-12-18 11:05:11ERRpanel [580152:639ee5d7ca4d5]Unable to get key: Repository is not opened
2022-12-18 11:05:11ERRpanel [580152:639ee5d7ca4d5]Unable to get key: Repository is not opened
2022-12-18 11:05:11ERRpanel [580152:639ee5d7ca4d5]Unable to get key: Repository is not opened

Peter Debik said:
How does that relate do https://support.plesk.com/hc/en-us/...en-SWKeyExFatalError-Repository-is-not-opened ? Have you fixed the file content as described in the article?
Click to expand...

Now I followed all steps of the article mentioned by Peter. I suppose we have to wait until tomorrow to see, whether it is solved now or not. Any idea how to test it directly?
 
2022-12-19 03:30:29ERRpanel [814933:639fccc52e65d]Unable to get key: Repository is not opened
2022-12-19 03:30:29ERRpanel [814933:639fccc52e65d]Unable to get key: Repository is not opened
2022-12-19 03:30:29ERRpanel [814933:639fccc52e65d]Unable to get key: Repository is not opened
2022-12-19 03:30:29ERRpanel [814933:639fccc52e65d]Unable to get key: Repository is not opened


Yesterday, I have followed the solution by https://support.plesk.com/hc/en-us/...en-SWKeyExFatalError-Repository-is-not-opened but it does not work in my case. Any further ideas?
 
I just checked the whole log and found, that 5th of November it happened first time, then one time each day

[2022-11-05 04:23:52.738] 1821513:6365d748b3d6c ERR [panel] Unable to get key: Repository is not opened
[2022-11-05 04:23:52.752] 1821513:6365d748b3d6c ERR [panel] Unable to get key: Repository is not opened
[2022-11-05 04:23:52.753] 1821513:6365d748b3d6c ERR [panel] Unable to get key: Repository is not opened
[2022-11-05 04:23:52.784] 1821513:6365d748b3d6c ERR [panel] Unable to get key: Repository is not opened
 
If you want through all the steps including manually retrieving the licence key again and it still does not work, this needs to be looked at by support. I am not exactly sure whether it should be licencing support or tech support in the first place. I think it is a technical problem, so I ask you to please submit a ticket to tech support and refer them to this thread here
https://talk.plesk.com/threads/unable-to-get-key-repository-is-not-opened.367560
I also recommend to install the Plesk Support SSH extension and give them access to your server so that they can check the issue directly on your server.

support.plesk.com

How to get support directly from Plesk?

Question How to get support directly from Plesk? Answer Lease-type Plesk licenses purchased directly from Plesk running on supported Plesk version include full free support. Perpetual-type license...
support.plesk.com support.plesk.com
 
I guess, you are right. I will start with a ticket next year when I have more time to go through the drush problem, too:) However, thank you for your kind help:)
 
Peter Debik said:
You're welcome. Please let us know what the results were.
Click to expand...
So, I discussed my problem with the Plesk support (which are very quick by the way:)) and they recommended the same procedure as done before as a starting point.

So I did again

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
I did - and the error message did not appear again.

Well I will wait whether this little IT-wonder will persist. If not, I`ll let you know how we eventually solve it.
 
You must log in or register to reply here.

Similar threads

Azsak
Issue Could not open Repository at "/etc/sw/keys": Invalid repository: unknown or unsupported format
Replies
2
Views
1K
Peter Debik
P
S
Issue Plesk Panel keep redirecting when trying to login Admin Panel
Replies
7
Views
2K
IgorG
IgorG
E
Question Unable to log in to Plesk via SSH.
Replies
5
Views
1K
Peter Debik
P
A
Question Upgrade Almalinux 8 to 9 with Plesk installed
Replies
2
Views
410
ansgar
A
david82
Resolved error update RPM-GPG-KEY-city-fan.org
Replies
2
Views
2K
david82
david82
Back
Top