Return To The uDownload Reference Site




  1. For Absolute Beginners
  2. Server Error
  3. Script Is Displayed, Not Executed
  4. Script Is Being Downloaded, Not Executed
  5. General "Unable to open" Errors
  6. Unable to locate LWP::UserAgent or Crypt::SSLeay Errors


1. For Absolute Beginners

If you've never installed or executed any Perl scripts on your server before, it is recommended that you first try installing our basic test script as described at our reference site:

http://www.uburst.com/uDownload/testscript.html

This simple Perl script is the most basic of Perl scripts and should help you to understand how to install and execute scripts on your server. It also will verify that your web hosting account is configured properly to run Perl scripts and will make installing the uDownload script that much easier.



2. Server Error

Upon installing the script on your server, the first thing you should do is use your browser to test the script by going to the URL of the script on your server. Upon doing so, you should see uDownload Login Form, similar to when you go to the URL script on our site:

http://www.uburst.com/cgi-bin/udownload/demo/udownload.pl

If when going to the URL of the script on your server you get a "Server Error" instead, then the problem is usually one of three things:

  1. The path to Perl is incorrect.
    The Path to perl is specified as the very first line of the CGI scripts. Typical values are /usr/bin/perl, /usr/local/bin/perl/ and /bin/perl. If you do not know what the path to perl is on your server, then you can ask your web hosting provider. NOTE: When specifying this path to perl, you must include the "#!" in front of the path. Example: #!/usr/bin/perl

  2. The file was transferred in BINARY mode (as opposed to ASCII or TEXT mode).
    When transferring the CGI script to your server, you must transfer it in ASCII or TEXT mode - as opposed to BINARY mode. Your FTP program should give you an option to do this - so be sure to transfer the CGI script in ASCII or TEXT mode.

  3. The script does not have execute permissions.
    Once the CGI script is transferred to your CGI directory on your server, you must change the permissions to READ and EXECUTE (chmod 755). If your server is a UNIX server, you should be able to change the file's permissions via your FTP program. If your server is an NT server, then you may have to get your web hosting provider to make the file executable.


3. Script Is Displayed, Not Executed

Upon installing the script on your server, the first thing you should do is use your browser to test the script by going to the URL of the script on your server. Upon doing so, you should see uDownload Login Form, similar to when you go to the URL script on our site:

http://www.uburst.com/cgi-bin/udownload/demo/udownload.pl

If when going to the URL of the script on your server, the script is displayed instead of being executed, then the problem is usually one of three things:

  1. The CGI script does not have the correct file extension for your server.
    That is, some servers are configured to only execute scripts that end in .pl and others are configured to only execute scripts that end in .cgi. Check with your web hosting server and rename the file if necessary.

  2. The directory that you put the script is not configured to execute CGI scripts.
    That is, usually your web hosting service will have to make a special directory for you to put your cgi scripts in such as cgi-bin or cgi-local. Again you can check with your web hosting provider.

  3. The permissions on the script itself are not correct.
    That is, you must make sure the script has read and execute permissions. This can be done with your FTP program on UNIX machines (chmod 755). People using NT servers, may have to get their web hosting service to change the permissions to executable for them.


4. Script Is Being Downloaded, Not Executed

Upon installing the script on your server, the first thing you should do is use your browser to test the script by going to the URL of the script on your server. Upon doing so, you should see uDownload Login Form, similar to when you go to the URL script on our site:

http://www.uburst.com/cgi-bin/udownload/demo/udownload.pl

If when going to the URL of the script on your server, the script tries to be downloaded instead of being executed, then the problem is usually one of three things:

  1. The CGI script does not have the correct file extension for your server.
    That is, some servers are configured to only execute scripts that end in .pl and others are configured to only execute scripts that end in .cgi. Check with your web hosting server and rename the file if necessary.

  2. The directory that you put the script is not configured to execute CGI scripts.
    That is, usually your web hosting service will have to make a special directory for you to put your cgi scripts in such as cgi-bin or cgi-local. Again you can check with your web hosting provider.

  3. The permissions on the script itself are not correct.
    That is, you must make sure the script has read and execute permissions. This can be done with your FTP program on UNIX machines (chmod 755). People using NT servers, may have to get their web hosting service to change the permissions to executable for them.


5. General "Unable to open" Errors

"Unable to open " Errors, are usually caused by one of two things:

  1. The path to your "download" directory is incorrect.
    That is, the directory path that you configured in question #5 of the script setup is not correct. Double-check the value of this setting or if possible, try using the Full Directory Path to your "download" directory instead of just a relative directory path. An example full path might be something like:

    $download_directory = "/www/youraccount/cgi-bin/downloads/";

    ...on UNIX servers, or perhaps something like this:

    $download_directory = "C:/users/youraccount/cgi-bin/downloads/";

    ....on NT servers.

    Note that this is a directory path...not a URL. So it won't start with "http". If you don't know the full path to your cgi-bin directory, then ask your web hosting provider.

  2. Your "download" directory does not have read/write/execute permissions.
    Try giving the directory full READ/WRITE permissions. On UNIX servers, this can be done via a chmod 777. On NT servers, you may have to contact your web hosting provider to make sure your "download" directory has READ/WRITE permissions.


6. Unable to locate LWP::UserAgent or Crypt::SSLeay Errors

Unable to locate "LWP::UserAgent" or "Crypt::SSLeay" errors indicate that the perl packages LWP or Crypt are not found on your server. Unless you are using uDownload's 3rd party interface (to automate license assignments), the easy way to correct this error is to comment out the contents of the "postToURL" subroutine in the udownload.pl script. To comment out the contents of the "postToURL" subroutine:

  1. Make a backup of your current udownload.pl script... just in case.


  2. Open your udownload.pl script with any text editor such as WordPad.


  3. Locate the start of the postToURL subroutine by searching for the following line:

    sub postToURL


  4. Delete (or comment out with # signs) all of the lines in that subroutine such that the subroutine is simply:

    sub postToURL
    {
    return $responseString;
    }


  5. Save the script...as TEXT if your editor asks... and try it out!

----------

  • If you didn't find a solution to your problem here, don't forget about our Support Forum.

  • And if that still doesn't solve your problem, you can submit a support request to us via our Support Request Form.