• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

rebuild apache on Plesk 8.2.1/FreeBSD

C

curtis

Guest
Hi,

Wondering if anyone has had any luck updating Plesk to the latest Apache 2.0.x on the FreeBSD platform? I have updated the FreeBSD to 6.2p9 on a couple of our servers with no problem, but that still leaves Plesk with an insecure version of Apache...

Not to mention that trying to update the openssl (via linking libssl.so.4 -> libssl.so.5) kills Apache. Any advice on this? I'm guessing that I could either update to the latest (old) version of OpenSSL to be libssl.so.4 maybe? What version would that be? I'd like to get these patched up and would appreciate any advice.

Thanks,
Curtis
 
You must log in or register to reply here.

Similar threads

T
Resolved After plesk upgrade to 18.0.78, ProFTPD terminating (signal 11)
Replies
7
Views
4K
Sofiia Kulish
Sofiia Kulish
I
Question CVE-2026-23918, CVE-2026-24072 and update to Apache 2.4.67
Replies
10
Views
14K
iainh
I
T
Question Unable to Identify User Who Enabled or Disabled Apache Module in Plesk
Replies
1
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
T
Issue ModSecurity / Imunify360 WAF rules update warning on LiteSpeed server
Replies
3
Views
3K
Xheni Rapushaj
X
H.W.B
Issue Watchdog down after Plesk update
Replies
7
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top