• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Plesk 18.0.81 Update #7 breaks AJP connectors for some applications

We have installed Plesk Obsidian 18.0.82.3, but on enabling the module...
Code:
plesk sbin httpd_modules_ctl -e proxy_lock
...we still get 403s:

proxy_lock: refused proxy backend ajp://localhost:8008/favicon.ico for /favicon.ico
Apache config in "vhost_ssl.conf":
Code:
# Proxy for JIRA
ProxyPass / ajp://localhost:8008/
ProxyPassReverse / ajp://localhost:8008/

Is there anything else to do besides the update and restarting Apache?
 
@mizar

A thing to note, I have two Ubuntu 24.04.5 LTS machines with Plesk Obsidian 18.0.82.3, with

libapache2-mod-proxy-lock-plesk 1.0-v.ubuntu.24.04+p18.0.83.0+t261030.2050

on one machine (updated first), and

libapache2-mod-proxy-lock-plesk 1.0-v.ubuntu.24.04+p18.0.82.3+t261111.1335

on the other machine (updated last, yesterday to be precise).

There is an issue with the packages !

Can you confirm that both packages are patched?

Kind regards....

PS The difference between the two machines is the kernel version ....... and there is the difference in time of updating.
 
@mizar

A thing to note, I have two Ubuntu 24.04.5 LTS machines with Plesk Obsidian 18.0.82.3, with

libapache2-mod-proxy-lock-plesk 1.0-v.ubuntu.24.04+p18.0.83.0+t261030.2050

on one machine (updated first), and

libapache2-mod-proxy-lock-plesk 1.0-v.ubuntu.24.04+p18.0.82.3+t261111.1335

on the other machine (updated last, yesterday to be precise).

There is an issue with the packages !

Can you confirm that both packages are patched?

Kind regards....

PS The difference between the two machines is the kernel version ....... and there is the difference in time of updating.
Hello,

Going to check. However, the packages seems not updated, because they has build date 261030, but should 2611*.
 
@mizar

It is - very likely - not kernel related : did some testing with old kernels (up til 88) and some newer kernels (111 and 149) and no difference.

The thing here is that

- there is a symptom : the older libapache2-mod-proxy-lock-plesk package
- there is an issue : the old package cannot be updated with apt-get or similar.

Any thoughts or tips on what I can test to get the latest proxy-lock package?

Please note that the symptom is related to an early push of Plesk 18.0.82.3, followed by a later push of a Plesk 18.0.82.3 with different packages.

Kind regards...
 
@mizar

It is - very likely - not kernel related : did some testing with old kernels (up til 88) and some newer kernels (111 and 149) and no difference.

The thing here is that

- there is a symptom : the older libapache2-mod-proxy-lock-plesk package
- there is an issue : the old package cannot be updated with apt-get or similar.

Any thoughts or tips on what I can test to get the latest proxy-lock package?

Please note that the symptom is related to an early push of Plesk 18.0.82.3, followed by a later push of a Plesk 18.0.82.3 with different packages.

Kind regards...
Unfortunately plesk installer write Plesk repo only on time of it's execution, so it will be a bit hacky:
* In one console run `plesk installer`, go to component selection
* On other console run `apt update` and `apt install `apt install libapache2-mod-proxy-lock-plesk`. Then if new package was installed, restart apache
* Exit from plesk installer in first console
 
@mizar,

This is an odd, but valuable "hacky" workaround, but it does not work.

More importantly, it simply results in an indication that more packages have not been updated properly.

Both machines are now on kernel 6.8.0-149-generic.

Using your hack, the (problematic) machine with the old proxy lock package now shows :

plesk-libpoco-1.15.4/noble 1.15.4-ubuntu.24.04.261111.0627 amd64 [upgradable from: 1.15.4-ubuntu.24.04.261025.2147]
plesk-python3-regex/noble 2023.8.8-v.ubuntu.24.04+p18.0.82.0+t260928.0632 amd64 [upgradable from: 2023.8.8-v.ubuntu.24.04+p18.0.74.0+t251014.1018]
sw-tar/noble 1.34-v.ubuntu.24.04+p18.0.82.0+t261013.0015 amd64 [upgradable from: 1.34-v.ubuntu.24.04+p18.0.61.0+t240426.1307]
N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension

when running apt list --upgradable.

Using your hack, the other machine now shows :

plesk-python3-regex/noble 2023.8.8-v.ubuntu.24.04+p18.0.82.0+t260928.0632 amd64 [upgradable from: 2023.8.8-v.ubuntu.24.04+p18.0.74.0+t251014.1018]
sw-tar/noble 1.34-v.ubuntu.24.04+p18.0.82.0+t261013.0015 amd64 [upgradable from: 1.34-v.ubuntu.24.04+p18.0.61.0+t240426.1307]
N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension


In short, the "hacky" workaround

a) does not resolve the issue with the older libapache2-mod-proxy-lock-plesk package

b) does provide a clear indication that other packages were also not updated with MU3 on Plesk 18.0.82


I will post this now, so you can proceed.

In addition, I will try to apply some updates with your workaround - if necessary, I will edit this post to update you.


Kind regards....
 
@mizar,

Similar issue occurred with Imunify360 - some packages should be updateable, but they are not shown.

There is a package related issue that seems to originating to and/or limited to 12 november, one of the first days of Plesk 18.0.82 MU3.

For Imunify360, the file

2026-11-12 15:03 rollout.imunify360.com_ubuntu_24.04_slot-10_dists_noble_main_binary-amd64_Packages

was missing in /var/lib/apt/lists.

Adding that file resolves the Imunify360 package issue.

The command apt policy <imunify_package_name> now again provides the proper results.

EDIT : the packages required to INSTALL updates STILL cause an issue. Updates (packages) can NOT be installed.

Kind regards....
 
Last edited:
Back
Top