These errors are, unfortunately, difficult to solve. There
is no single solution: the fix depends on how your server is
configured, and server configurations differ
drastically.
THINGS TO TRY WHETHER YOU GET A 500 OR 403
ERROR:
- Ensure that you have CHMODded newspro.cgi 755 - try again.
If it still doesn't work, try a CHMOD of 777.
- If there is a file called .htaccess in your NewsPro directory, try deleting it.
- Try running another CGI script in the same directory. If
you can't, it's certain that it's a problem with your
settings.
- If none of these suggestions work, contact your web
host's support department. Don't contact NewsPro support,
as these errors are server-specific, and we're not familiar
with your server. |
IF
YOU GET A 500 SERVER ERROR:
- Try re-uploading all files, making sure that you do so in ASCII
mode.
- Ensure that the first line of newspro.cgi points to the
path to Perl on your server. If you're not sure of the
path, look at your web host's support information. The path
must point to a version of Perl 5; NewsPro will not work
with Perl 4.
- Try filling out the Server Problems Workarounds section
of newspro.cgi.
- Try changing the $IIS variable in newspro.cgi (near the
top). |
IF
YOU GET A 403 FORBIDDEN ERROR:
- Check if you are allowed to run CGI scripts in the directory you are
installing NewsPro in. Try another directory (if the error-
producing copy is in a cgi-bin directory, try a directory
outside the cgi-bin, and vice versa).
- Try renaming newspro.cgi to newspro.pl.
- CHMOD the directory that newspro.cgi is in 777. If that
doesn't work, try 755. |
|