• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Plesk is not detecting new extension updates

Amadex

Basic Pleskian
Server operating system version
CL 7 & 8
Plesk version and microupdate number
Plesk Obsidian 18.0.65 Update 2
Hello,

I have two servers with latest Plesk (18.0.65 Update 2), one of them is using CloudLinux 7 and another is using CloudLinux 8.

Both of them are not detecting new extension updates. E.g The latest log browser is 1.9.6, but on mine servers are this version and there's no update:

o2xPpbk.png

GutSZAb.png


I always update my servers like this:
Code:
yum clean all
yum update -y
plesk installer --select-release-latest --upgrade-installed-components
 
Extension updates are controlled from the extension catalog URL set in panel.ini.

Furthermore, extensions might not be available on older Plesk or OS versions.

You can curl the Plesk extension catalog on each server to see what versions are returned for both your servers. The output will be json and you can pass the output via jq.
 
Extension updates are controlled from the extension catalog URL set in panel.ini.

Furthermore, extensions might not be available on older Plesk or OS versions.

You can curl the Plesk extension catalog on each server to see what versions are returned for both your servers. The output will be json and you can pass the output via jq.
CL 8 is not old.
 
Do you have any customizations to the panel.ini for the extensions? Some providers do add there their own extension catalog mirror.
 
This is our panel.ini, same on both servers.

Code:
; Plesk initialization file
;
; Notes:
; * Be careful and understand what do you do while modifying of panel behavior.
; * If option is missed default value will be used.
; * Use ";" for comments.
; * Enabled debug mode or high log level can be the reason of panel slowdown.

[debug]

; Enable debug mode (do not use in production environment)
;enabled = on

[log]

; Log messages verbosity level (from 0 to 7)
; 0 - only critical errors, 7 - all including debug messages, default - 3
;filter.priority = 7

; Enable logging of SQL queries
;show.sql_query = on

; Enable logging of external utilities calls
;show.util_exec = on

; Enable logging of stdin and stdout for external utilities calls (do not use in production environment)
;show.util_exec_io = on

; Enable logging of APSC activities
;apsc.enabled = on

[aps]

; Disable APS apps at all
;enabled = off

[locale]

; Show locale keys instead of localized string (values: off, on, long)
;showKeys = long

[help]

; Documentation URL
;url = http://example.com

[promos]

; Disable other products promotions
;enabled = off

[facebook]

; Hide Like link
;showLikeLink = off

[rating]

; Hide feedback dialog with question to rate product
;enabled = off

[cli]

; Ignore nonexistent options in command line interface
;ignoreNonexistentOptions = off

[pmm]

; Allow to upload modified, corrupted, created on another server or in an older Panel version
; that does not support signing of backups. Set this option only if you trust to backup creator because upload of modified
; backup may compromise you server. If value is on then users just informed about changes in backup and restore isn't blocked
; Values: on, off
;allowRestoreModifiedDumps = off

[domainManagement]
settings.favicons = false

[navigation]
newHomeView.enabled = true
 
If you go to Extensions > Updates > Check Now, do you get the same version/update to the latest extension version?
 
Hm... Are there any errors/traces/clues in the Plesk "panel.log" related to the Extension Catalog?
 
It is possible to provide a custom extension catalog URL as a key property. Could you please check the `/usr/local/psa/admin/conf/customizations.conf` file as well?
 
It is possible to provide a custom extension catalog URL as a key property. Could you please check the `/usr/local/psa/admin/conf/customizations.conf` file as well?
Code:
[root@plesk01 ~]# cat /usr/local/psa/admin/conf/customizations.conf
{"serverSettingsVersion":"plesk-1","ini":{"leika":{"experiments":true,"trafficSource":"partners"}}}[root@plesk01 ~]#
 
Does it work when you change partners to NFR?
Code:
{"serverSettingsVersion":"plesk-1","ini":{"leika":{"experiments":true,"trafficSource":"NFR"}}}
 
Could you please run the next command on the server to check IP addresses and certificates,
wget https://ext.plesk.com and provide the output (like here Issue - Extensions and firewall dont show up)
Code:
[root@plesk01 ~]# wget https://ext.plesk.com
--2024-12-03 15:06:18--  https://ext.plesk.com/
Resolving ext.plesk.com (ext.plesk.com)... xxx.xxx.xxx.xx
Connecting to ext.plesk.com (ext.plesk.com)|xxx.xxx.xxx.xx|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 0
Saving to: ‘index.html’

    [ <=>                                                                                                                                                                                                                ] 0           --.-K/s   in 0s     

2024-12-03 15:06:18 (0.00 B/s) - ‘index.html’ saved [0/0]
 
Back
Top