• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

Install mod_proxy on Plesk 8.1 FreeBSD 6.2 apache 2.0

T

TDuncklee

Guest
Has anyone running FreeBSD with apache2.0 gotten mod_proxy installed? I’ve managed to get it installed on a test server but broken other things. The closest I’ve gotten is to build apache with every module listed like this:

make WITH_MODULES="access auth auth_anon auth_dbm auth_digest file_cache charset_lite cache disk_cache include deflate log_config env mime_magic cern_meta expires headers usertrack unique_id setenvif ssl mime dav status autoindex asis info suexec cgi dav_fs vhost_alias negotiation dir imap actions speling userdir alias rewrite suexec perl logio python libphp5 fcgid actions proxy proxy_ftp proxy_http proxy_connect"

Now when I go to a plesk installed default index page the lower portion with the icons for testing php, perl, etc. do not load. Just says “Loading...†where the icons used to be.

Can anyone tell me the "correct" way to get mod_proxy working with apache2 on FreeBSD and not break anything else?

TD
 
Back
Top