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

installing Coldfusion MX 7 and configuring with Apache 2.0.52

R

rocco@

Guest
I was just wondering if anyone has been able to install Coldfusion MX 7 on a system with Plesk 8.1 and successfully configured it to work with Apache.

Installing it is fine. I can get Coldfusion to serve through port 8500. As soon as I run the apache_connector.sh script, things go south. Apache does not see Coldfusion and any cfm pages put in the www root folder results in a 404.

This is a dedicated virtual server through mediatemple. It is running CentOS 4.4.

Any thoughts out there?

Thanks!
 
Looks like I found the culprit

I wasn't installing Coldfusion with apache as the runtime user. I originally created a cfuser account for cf to use. Well, no wonder Coldfusion didn't have permission to serve anything in apache. Wow... only took two weeks to figure out.
 
Back
Top