• 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:
Yeah, I found that new version of mod_proxy_lock package does not installed, and created the issue with id PPP-73985. At this moment you can only manually donwload and install the fixed version using dpkg, for example for Ubuntu 24.04 the command will be `wget https://autoinstall.plesk.com/pool/...buntu.24.04+p18.0.82.3+t261111.1335_amd64.deb && dpkg -i ./libapache2-mod-proxy-lock-plesk_1.0-v.ubuntu.24.04+p18.0.82.3+t261111.1335_amd64.deb`
 
Yeah, I found that new version of mod_proxy_lock package does not installed, and created the issue with id PPP-73985. At this moment you can only manually donwload and install the fixed version using dpkg, for example for Ubuntu 24.04 the command will be `wget https://autoinstall.plesk.com/pool/...buntu.24.04+p18.0.82.3+t261111.1335_amd64.deb && dpkg -i ./libapache2-mod-proxy-lock-plesk_1.0-v.ubuntu.24.04+p18.0.82.3+t261111.1335_amd64.deb`

@mizar

Tested the fix and that worked like a charm.

Two notes :

1 - apache2 seems to be restarting / reloading - is it correct to assume that apache does not have to be restarted?

2 - I was working in multiple terminals and - accidentally - executed the fix in the terminal where I was working in /var/cache/apt/archives - this should not be an issue though, but I noticed these packages being present :

-rw-r--r-- 1 root root 4.0K 2026-11-02 17:59 libapache2-mod-proxy-lock-plesk_1.0-v.ubuntu.24.04+p18.0.81.7+t261102.1556_amd64.deb
-rw-r--r-- 1 root root 4.0K 2026-11-11 14:41 libapache2-mod-proxy-lock-plesk_1.0-v.ubuntu.24.04+p18.0.82.3+t261111.1335_amd64.deb
-rw-r--r-- 1 root root 4.0K 2026-11-02 15:44 libapache2-mod-proxy-lock-plesk_1.0-v.ubuntu.24.04+p18.0.83.0+t261030.2050_amd64.deb

hence implying that the libapache2-mod-proxy-lock-plesk_1.0-v.ubuntu.24.04+p18.0.81.7+t261102.1556_amd64.deb package was also not installed.

That is, a package was held back before the Plesk 18.0.82 MU3 update (read: before automatic Plesk updates installed MU3).

Is there any - reasonable - explanation for this odd behavior of packages being held back on Ubuntu 24.04.5 LTS machines?

Might there be some issue with Plesk 18.0.82 MU2 that was not properly patched in MU3?

I am really at a loss here, searching for answers.

Kind regards........
 
> apache2 seems to be restarting / reloading - is it correct to assume that apache does not have to be restarted?

Yes, forgot this step, manual package installation require apache restart afterwards.

> I was working in multiple terminals and - accidentally - executed the fix in the terminal where I was working in /var/cache/apt/archives - this should not be an issue though, but I noticed these packages being present

Isn't it means that the server was recently updated from 18.0.81?

> Might there be some issue with Plesk 18.0.82 MU2 that was not properly patched in MU3?

In short, there is the problem that the version of the package was not correcly increased, and the package for 82.3 was built with lesser release then 82.2, and thus it is not updated.
 
Not sure about this

Isn't it means that the server was recently updated from 18.0.81?

since I am not sure whether it jumped from 18.0.81.7 or 18.0.81.8 to 18.0.82.2.

The reason why I am not sure is the simple fact that is should not have jumped at all : the server was not configured to install macro updates automatically (and micro updates were configured to be installed automatically).

This statement

In short, there is the problem that the version of the package was not correcly increased, and the package for 82.3 was built with lesser release then 82.2, and thus it is not updated.

is a bit odd, but I can misinterpret that one.

How is it even possible that a 18.0.82.2 instance is present and/or recognized, if the Plesk instance - actually - concerns a lesser release (like 18.0.81.x)?

In essence, it seems to be the case that you state that specific update paths towards 18.0.82.3 are not working properly - that is, if I am not mistaken.

More importantly, how to resolve / repair this?
 
@mizar

Let me rephrase my answers, since the presence of certain packages seem to give another indication.

The answer to the question

Isn't it means that the server was recently updated from 18.0.81?

would be : yes, it is updated ......... but not in the way one might expect.

The package

libapache2-mod-proxy-lock-plesk_1.0-v.ubuntu.24.04+p18.0.81.7+t261102.1556_amd64.deb

was replaced by / updated to

libapache2-mod-proxy-lock-plesk_1.0-v.ubuntu.24.04+p18.0.83.0+t261030.2050_amd64.deb

since the proper package was not present at all.

A clear indication of the above is the simple fact that the update to 18.0.82.3 (from whatever previous version) is jumping to 18.0.83.0 - a release candidate.

This statement

In short, there is the problem that the version of the package was not correcly increased, and the package for 82.3 was built with lesser release then 82.2, and thus it is not updated.

is hence not correct.

Upon update to 18.0.82.3 (on or around November 12), the 18.0.83 package of libapache2-mod-proxy-lock-plesk was - somehow - installed.

It is not a lesser release, but a greater release (18.0.83.0) that prevents updating to 18.0.82.3 package of libapache2-mod-proxy-lock-plesk.

This is also confirmed when doing the dpkg based installation : it gives a warning that a package is downgraded.

I did not see that before, my mistake.


Still, there are the issues with the package lists not being correct.

A plesk repair installation will probably not help at all - is that correct?


Kind regards...
 
> A clear indication of the above is the simple fact that the update to 18.0.82.3 (from whatever previous version) is jumping to 18.0.83.0 - a release candidate.

It is not a release candindate actually. It's normal that some packages has such release. There is not normal that new update's packages has lesser release then previous.

> Upon update to 18.0.82.3 (on or around November 12), the 18.0.83 package of libapache2-mod-proxy-lock-plesk was - somehow - installed.
>
> It is not a lesser release, but a greater release (18.0.83.0) that prevents updating to 18.0.82.3 package of libapache2-mod-proxy-lock-plesk.

That's exacly what i said, previous update 18.0.82.2 has libapache2-mod-proxy-lock-plesk with *greater* release then 18.0.82.3, and thus, the new package is not installed.

> Still, there are the issues with the package lists not being correct.

Could you please tell what the issue with packages lists was? I see only imunify360 mentions
 
@mizar,

This

That's exacly what i said, previous update 18.0.82.2 has libapache2-mod-proxy-lock-plesk with *greater* release then 18.0.82.3, and thus, the new package is not installed.

became clear later to me, my apologies for the confusion.


In essence, I was a bit overwhelmed by the fact that two - exactly - identical servers were different somehow, with the only difference that one of the server being updated automatically (the dev server, if we need to assign a name) and the other one being updated manually (a couple of days later).

Setup and config should have been exactly the same, with one or two differences (that should not matter for this issue).


The Imunify conflict is remaining and resulting in even more mind-blowing situations.

This might be related to one of the differences between the two servers : I did install (in the past) Imunify via CLI on one server and with Plesk GUI on the other server, but the CLI install has been reverted to a Plesk based installation.

The nasty thing about Imunify is that packages are not cleaned properly when uinstalling Imunify via either Plesk or CLI - a lot of manual action is required.

At this moment, there is this odd situation that both servers install / update different packages and package versions, which can be related to

a) the (past) Plesk based installation : there is an indication of that, but no certainty

b) the "roll out" of Imunify updates : not all things are updated simultaneously


It seems to be the case that the "roll out" repos are not properly synchronized, but I cannot confirm that.

There is a (constant) difference in the roll out repo used by both servers.


In my humble opinion, this is not a good thing and Plesk should take it up with Imunify / CloudLinux ....... but then again, it is up to Imunify / CloudLinux.

If and when I have time, I will contact Imunify / CloudLinux.


There are - potentially - many other conflicts, but I cannot establish them with certainty, so it is - relatively - safe to ignore the other conflicts.


One other matter of importance might be that Plesk leaves a lot of obsolete packages.

Can an automated clean-up of packages be adding to a next Plesk micro update?


Kind regards....

PS I hope that PPP-73985 will be resolved (and a patch released soon), since it is likely that some Plesk instance might be affected.
 
Last edited:
Back
Top