Issue Extension manager lost

[HenningM]

Dear Community,

my extension manager is gone. I can't install any extension from plesk anymore.
It is on Unix CentOS 7, Plesk 17.8 Update #5.

Anyone have an idea?

Kind regards
Henning

 

[Brujo]

Not a answer who resolve your issue but it seems you hit the same issue as some other in this thread
Issue - Extension Manager Missing - Can't install Extensions after upgrade

 

[Sergio Manzi]

my extension manager is gone.

Have you tried using a different browser?
Do you have any adblocker installed? I wouldn't be much surprised if this is the cause...

 

[HenningM]

Have you tried using a different browser?
Do you have any adblocker installed? I wouldn't be much surprised if this is the cause...

Just checked. Any add-on disabled, same issue.

 

[Sergio Manzi]

 

[Aleksandr Dunaev]

Hi, HenningM!

Try this solution:
Extensions menu is missing after the upgrade from Onyx 17.5 to Onyx 17.8 on Linux

 

[MSZ]

This did the trick for me.
3 steps, then re-login + Page-Refresh (Shift+F5) and Extensions showing.

 

[Bitpalast]

@Aleksandr Dunaev

Try this solution:
Extensions menu is missing after the upgrade from Onyx 17.5 to Onyx 17.8 on Linux

Not a publicly accessible article.

 

[danami]

I'm not sure if this is related but I was having trouble accessing the extension directory in some of my test VMs and it was because the SSL certificate for Plesk Extensions was showing as "Issued certificate is not yet valid".

Example:

[root@test3 ~]# wget "https://ext.plesk.com/api/v2/packages?playform=unix&version=18.02&ai-compatible"
--2019-10-02 02:38:56--  https://ext.plesk.com/api/v2/packages?playform=unix&version=18.02&ai-compatible
Resolving ext.plesk.com (ext.plesk.com)... 185.246.209.10
Connecting to ext.plesk.com (ext.plesk.com)|185.246.209.10|:443... connected.
ERROR: cannot verify ext.plesk.com's certificate, issued by ‘/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3’:
  Issued certificate not yet valid.
To connect to ext.plesk.com insecurely, use `--no-check-certificate'.

It turns out that my server time was off by a bit and re-syncing the server time fixed the problems accessing the extension directory.

 

[Anthony]

Hello, the issue is confirmed and registered as EXTCATALOG-306. It will be fixed by publishing the new version of the Extensions Catalog on Monday (November 25).