@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....