The Problem

After following the Coranto install instructions and then accessing coranto.cgi for the first time using h**p:// you are greeted with a blank screen. Upon viewing the source code for the blank page you see:

 <html><head><title>Coranto: Fatal Error</title>

There are two common causes for this problem.

  • wrong path info
  • flock problem

If this has started on an existing and previously working Coranto install it is very likely that your hosting company has made changes on the server.

  • moved your site to a different server
  • moved your site's physical location on the server
  • changed a policy (now confining cgi scripts to the cgi-bin when they previously didn't)

If Coranto just stopped working check for changes with your host.

↑ Contents

Path Settings

One possible culprit in this case is improper path information. Coranto usually does a good job of detecting the proper path information. If it doesn't you may have to specify the path in the coranto.cgi file. Open the file in a text editor and find this section:

# Coranto tries to determine its path and URL automatically. This works in 90%
# of cases, but some servers aren't cooperative and don't allow this information
# to be found automatically. Though it won't hurt, there's no need to fill this out
# unless you encounter problems.
# If you encounter problems (particularly with incorrect URLs, or fatal error messages
# about files not being found), fill in the two variables below.

$abspath = '';
# Set the above to the absolute path to Coranto's directory, without
# a trailing slash. Example:
# $abspath = '/absolute/path/to/coranto';

$scripturl = '';
# Set the above to the URL to coranto.cgi. Example:
# $scripturl = '';

Remove the # at the start of the $abspath line and the $scripturl line and enter the correct information for your server. $abspath is the path from the root of your webserver and the $scripturl is the URL you would enter in your browser to access the script.

Save the file and upload to your server.

Use php to discover absolute path

<?php echo $_SERVER['DOCUMENT_ROOT']; ?>

Save the above code as path.php upload to the directory you want the absolute path for call in your browser h**p://

Use perl to discover your absolute path


print "Content-type: text/html\n\n";
print "<html>\n" ;
print "<body>\n";
print "Perl version: $]<br>\n";
print "Absolute path: $ENV{'SCRIPT_FILENAME'}<br>\n";
print "</body>\n";
print "</html>\n";

Save as path.cgi (using unix/linux line endings) upload to the directory you want the info for chmod to 755 call in your browser h**p://

↑ Contents

  • The path to perl line (the first line) in any perl script can not be indented. It must be all the way to the left.
  • perl scripts running on unix/linux servers usually require that the line endings be unix


If your server does not support FLOCK you will need to turn it off. This happens more frequently on a Windows server. To disable FLOCK you must open the file and edit one of the settings available there. Here is the section you are looking for:

# File locking is a feature, provided by the operating system, which
# prevents possible serious problems when Coranto is being used by
# multiple users. Almost every operating system supports this, except
# for Windows 9x/ME. Possible settings:
# 2  Enable file locking. If you know your server supports it, set
#	UseFlock to this.
# 0  Disable file locking. This may result in file corruption.

$UseFlock = 2;

Change the 2 to a 0 (zero).

If you have previously used Coranto on the same server and did not have to change the setting for FLOCK then you probably need to set the path information.

↑ Contents

Page last modified on February 08, 2009, at 08:48 PM