• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Plesk novice: problems installing miva executable

Richard Grevers

New Pleskian
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Panel 10.4.4, CentOS 6, Apache, Virtuozzo

PROBLEM DESCRIPTION
Hi,
I'm migrating all my websites from a Kloxo server to a brand new Plesk VPS. I have a couple of legacy sites needing the miva empresa 3.97 interpreter - note that this is a different beast from the miva 5 Virtual machine which is supported within Plesk's domain options.

STEPS TO REPRODUCE

I have put the miva binary and its config file in /var/www/vhosts/[sitename]/cgi-bin and set permissions.
Then, following the instructions in the header of the plesk-generated conf file for the domain, I've created (via ssh) /var/www/vhosts/[sitename]/conf/vhost.conf as follows:

<VirtualHost 111.65.227.181:80>
ScriptAlias /miva /var/www/vhosts/opera.geek.nz/cgi-bin/miva

DirectoryIndex index.php index.mv index.html
AddType application/x-miva .mv
Action application/x-miva /miva
</VirtualHost>


(and reloaded or restarted apache)

ACTUAL RESULT
This has not worked: http://[sitename]/ brings up the apache default page (i deleted index.html) and http://[sitename]/index.mv displays the unprocessed script.

furthermore, when I put an unknown directive ('Booyah!') in the conf file, it fails to generate the expected 500 error - therefore I don't think the vhost.conf file is being read at all.

ANY ADDITIONAL INFORMATION

It's kind of urgent for me to get these sites working.
 
No, because that would not work.
Up until version 3.9, mivascript was an interpreted language. From version 4 onwards it is a compiled language running on a VM. (Miva Corp made a bad mistake in keeping the "Empresa" name for a totally different product. The Plesk setup includes version 5.x

These sites have dynamic function calls so can't be converted to compiled miva. Compiled miva uses a different file extension (.mvc)
I did install mivavm support for one site, just to see what the system created.
 
Latest progress after bashing away at this some more:
I confirmed that files I put in the domain's own conf folder are not getting parsed (but the plesk generated ones are). I haven't been able to find where in the apache conf file chain it sets up includes for virtual hosting.

I tried using .htaccess in the httpdocs directory, but things are locked down to the point of not allowing DirectoryIndex there, and of course you cannot use VirtualHost blocks or ScriptAlias in a .htaccess.

At the moment I have added index.mv to the DirectoryIndex in the global httpd.conf file (how will that survive upgrades?) and the addType in a .htaccess.

That's resulting in a premature end of script headers.

Unlike the newer miva, which uses SetEnv directives to configure it (allowing the binary to go in the server's global cgi-bin), the old miva needs to be at the Virtualhost level because it reads a conf file in its own directory, which points to the data directories.
 
Back
Top